tPostgresqlOutputBulkExec
Improves performance during Insert operations to a Postgresql database.
The tPostgresqlOutputBulkExec executes the Insert
action on the data provided.
The tPostgresqlOutputBulk and tPostgresqlBulkExec components are generally used together as part of a
two step process. In the first step, an output file is generated. In the second step,
this file is used in the INSERT operation used to feed a database. These two steps are
fused together in the tPostgresqlOutputBulkExec
component.
tPostgresqlOutputBulkExec Standard properties
These properties are used to configure tPostgresqlOutputBulkExec running in the Standard Job framework.
The Standard
tPostgresqlOutputBulkExec component belongs to the Databases family.
The component in this framework is available in all Talend
products.
connector. The properties related to database settings vary depending on your database
type selection. For more information about dynamic database connectors, see Dynamic database components.
Basic settings
Database |
Select a type of database from the list and click |
Property type |
Either Built-in or |
 |
Built-in: No property data stored |
 |
Repository: Select the repository |
DB Version |
List of database versions. |
Host |
Database server IP address. Currently, only localhost, |
Port |
Listening port number of DB server. |
Database |
Name of the database |
Schema |
Name of the schema. |
Username and |
DB user authentication data. To enter the password, click the […] button next to the |
Table |
Name of the table to be written. Note that only one table can be |
Action on table |
On the table defined, you can perform one of the following
None: No operation is carried
Drop and create table: The table is
Create table: The table does not
Create table if not exists: The
Drop table if exists and create:
Clear a table: The table content is |
File Name |
Name of the file to be generated and loaded. Warning:
This file is generated on the machine specified by the URI in |
Schema and Edit |
A schema is a row description, it defines the number of fields to Click Edit
|
 |
Built-In: You create and store the schema locally for this component |
 |
Repository: You have already created the schema and stored it in the When the schema to be reused has default values that are You can find more details about how to |
Advanced settings
Additional JDBC Parameters |
Specify additional JDBC parameters for the |
Action on data |
On the data of the table defined, you can perform:
Bulk Insert: Add multiple entries to the
Bulk Update: Make simultaneous changes |
Copy the OID for each row |
Retrieve the ID item for each row. |
Contains a header line with the names of each column |
Specify that the table contains header. |
Use local file for copy(for DB server 8.2 or newer) |
Select this check box to copy files from the PostgreSQL client machine. |
Encoding |
Select the encoding from the list or select CUSTOM and define it manually. This field is |
File type |
Select the type of file being handled. |
Null string |
String displayed to indicate that the value is null.. |
Row separator |
String (ex: ” |
Fields terminated by |
Character, string or regular expression to separate fields. |
Escape char |
Character of the row to be escaped. |
Text enclosure |
Character used to enclose text. |
Activate standard_conforming_string |
Activate the variable. |
Force not null for columns |
Define the columns nullability.
Force not null: Select the check box |
tStatCatcher Statistics |
Select this check box to collect log data at the component |
Enable parallel execution |
Select this check box to perform high-speed data processing, by treating
multiple data flows simultaneously. Note that this feature depends on the database or the application ability to handle multiple inserts in parallel as well as the number of CPU affected. In the Number of parallel executions field, either:
Note that when parallel execution is enabled, it is not possible to use global
|
Usage
Usage rule |
This component is mainly used when no particular transformation |
Limitation | The database server must be installed on the same machine where the Studio is installed or where the Job using tPostgresqlOutputBulkExec is deployed, so that the component functions properly. |
Related scenarios
For use cases in relation with tPostgresqlOutputBulkExec, see the following scenarios: