July 30, 2023

tPostgresqlBulkExec – Docs for ESB 7.x


Improves performance while carrying out the Insert operations to a Postgresql

The tPostgresqlBulkExec executes the Insert action on
the data provided.

The tPostgresqlOutputBulk and
tPostgresqlBulkExec components are used
together to first output the file that will be then used as parameter to execute the SQL
query stated. These two steps compose the tPostgresqlOutputBulkExec component, detailed in a separate section.
The interest in having two separate elements lies in the fact that it allows
transformations to be carried out before the data loading in the database.

tPostgresqlBulkExec Standard properties

These properties are used to configure tPostgresqlBulkExec running in the Standard Job framework.

The Standard
tPostgresqlBulkExec component belongs to the Databases family.

The component in this framework is available in all Talend

Note: This component is a specific version of a dynamic database
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


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
file in which the properties are stored. The fields that follow are
completed automatically using the data retrieved.

Use an existing connection

Select this check box and in the Component List click the relevant connection component to
reuse the connection details you already defined.

Note: When a Job contains the parent Job and the child Job, if you
need to share an existing connection between the two levels, for example, to share the
connection created by the parent Job with the child Job, you have to:

  1. In the parent level, register the database connection
    to be shared in the Basic
    view of the connection component which creates that very database

  2. In the child level, use a dedicated connection
    component to read that registered database connection.

For an example about how to share a database connection
across Job levels, see

Talend Studio
User Guide

DB Version

List of database versions.


Database server IP address


Listening port number of DB server.


Name of the database.


Name of the schema.

Username and

DB user authentication data.

To enter the password, click the […] button next to the
password field, and then in the pop-up dialog box enter the password between double quotes
and click OK to save the settings.


Name of the table to be written. Note that only one table can be
written at a time and that the table must exist for the insert
operation to succeed.

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
removed and created again.

Create table: The table does not
exist and gets created.

Create table if not exists: The
table is created if it does not exist.

Drop table if exists and create:
The table is removed if it already exists and created again.

Clear table: The table content is

Truncate table: The table content
is deleted. You don not have the possibility to rollback the

File Name

Name of the file to be loaded.


This file is located on the machine specified by the URI in
the Host field so it should be
on the same machine as the database server.

Schema and Edit

A schema is a row description, it defines the number of fields to
be processed and passed on to the next component. The schema is
either Built-in or stored remotely
in the Repository

Click Edit
to make changes to the schema. If the current schema is of the Repository type, three options are available:

  • View schema: choose this
    option to view the schema only.

  • Change to built-in property:
    choose this option to change the schema to Built-in for local changes.

  • Update repository connection:
    choose this option to change the schema stored in the repository and decide whether
    to propagate the changes to all the Jobs upon completion. If you just want to
    propagate the changes to the current Job, you can select No upon completion and choose this schema metadata
    again in the Repository Content


Built-In: You create and store the schema locally for this component


Repository: You have already created the schema and stored it in the
Repository. You can reuse it in various projects and Job designs.

When the schema to be reused has default values that are
integers or functions, ensure that these default values are not enclosed within
quotation marks. If they are, you must remove the quotation marks manually.

You can find more details about how to
verify default values in retrieved schema in Talend Help Center (https://help.talend.com).

Advanced settings

Additional JDBC Parameters

Specify additional JDBC parameters for the
database connection created.

This property is not available when the Use an existing connection
check box in the Basic settings view is selected.

Action on data

On the data of the table defined, you can perform:

Bulk Insert: Add multiple entries
to the table. If duplicates are found, job stops.

Bulk Update: Make simultaneous
changes to multiple entries.

Copy the OID for each row

Retrieve the ID item for each row.

Contains a header line with the names of each column in
the file

Specify that the table contains header.

File type

Select the type of file being handled.

Null string

String displayed to indicate that the value is null.

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 next to the column you want to define as not null.

tStatCatcher Statistics

Select this check box to collect log data at the component


Usage rule

This component is to be used along with tPostgresqlOutputBulk component. Used together, they
can offer gains in performance while feeding a Postgresql

Dynamic settings

Click the [+] button to add a row in the table
and fill the Code field with a context
variable to choose your database connection dynamically from multiple
connections planned in your Job. This feature is useful when you need to
access database tables having the same data structure but in different
databases, especially when you are working in an environment where you
cannot change your Job settings, for example, when your Job has to be
deployed and executed independent of Talend Studio.

The Dynamic settings table is
available only when the Use an existing
check box is selected in the Basic settings view. Once a dynamic parameter is
defined, the Component List box in the
Basic settings view becomes unusable.

For examples on using dynamic parameters, see Reading data from databases through context-based dynamic connections and Reading data from different MySQL databases using dynamically loaded connection parameters. For more information on Dynamic
and context variables, see Talend Studio
User Guide.

Related scenarios

Document get from Talend https://help.talend.com
Thank you for watching.
Notify of
Inline Feedbacks
View all comments
Would love your thoughts, please comment.x