# tELTPostgresqlMap Builds the SQL SELECT statement using the table schema(s) provided by one or more tELTPostgresqlInput components. The three ELT Postgresql components are closely related, in terms of their operating conditions. These components should be used to handle Postgresql database table schemas to generate SQL statements, including clauses, which are to be executed in the database output table defined. ## tELTPostgresqlMap Standard properties These properties are used to configure tELTPostgresqlMap running in the Standard Job framework. The Standard tELTPostgresqlMap component belongs to the ELT family. The component in this framework is available in all Talend products. ## Basic settings | Properties | Description | | --- | --- | | Use an existing connection | Select this check box and in the Component
List drop-down list, select the desired connection component to
reuse the connection details you already defined.

Information noteNote: When a Job contains the parent Job and the child Job, do the following if you
want to share an existing connection between the parent Job and the child Job (for example,
to share the connection created by the parent Job with the child Job).

  1. In the parent level, register the database connection to be shared in the Basic settings view of the connection component which creates that very database connection.
  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 [Sharing a database connection](https://help.qlik.com/talend/r/en-US/7.3/studio-user-guide/sharing-database-connection). | | ELT Postgresql Map Editor | The ELT Map editor allows you to define
the output schema and make a graphical build of the SQL statement to be
executed. The column names of schema can be different from the column
names in the database.

You can filter schema columns in an input or output table
by clicking the Enable/disable column name filter button in the
corresponding table and entering the search keyword in the field displayed.

You can click ![](https://help.qlik.com/talend/en-US/components/8.0/Resources/images/button-elt-map-setup-configuration.png) on the upper left
corner and in the Property Settings dialog box displayed, select the
Add quotes in columns when generating query check box to add
quotes for the column names in the generated SQL query. This check box is displayed as
Delimited identifiers if you have not installed the 8.0 R2022-11
Talend Studio
monthly update or a later one provided by Talend.

When using drag and drop to build group clause expressions, commas are
automatically added between column names. | | Style link | Select the way in which links are
displayed.


Auto: By default, the links between the
input and output schemas and the Web service parameters are in the form
of curves.


Bezier curve: Links between the schema
and the Web service parameters are in the form of curve.


Line: Links between the schema and the
Web service parameters are in the form of straight lines.

This option slightly optimizes
performance. | | Property type | | | Host | Database server IP address | | Port | Listening port number of DB server. | | Database | Name of the database | | Username and Password | DB user authentication data.

To enter the password, click the [...] button
next to the password field, enter the password in double quotes in the pop-up dialog box,
and click OK to save the settings. | ## Advanced settings | Properties | Description | | --- | --- | | Additional JDBC parameters | Specify additional connection properties
for the DB connection you are creating. This option is not available if
you have selected the Use an
existing connection check box in the Basic settings. | | tStatCatcher Statistics | Select this check box to gather the Job
processing metadata at a Job level as well as at each component
level. | ## Global Variables | Variables | Description | | --- | --- | | Global Variables | ERROR\_MESSAGE: the error message generated by the
component when an error occurs. This is an After variable and it returns a string. This
variable functions only if the Die on error checkbox is
cleared, if the component has this checkbox.

A Flow variable functions during the execution of a component
while an After variable functions after the execution of the component.

To fill up a field or expression with a variable, press Ctrl+Space to access the variable list and choose the variable to use from
it.

For more information about variables, see [Using contexts and variables](https://help.qlik.com/talend/r/en-US/8.0/studio-user-guide/contexts-and-variables). | ## Usage | Usage guidance | Description | | --- | --- | | **Usage rule** | tELTPostgresqlMap is used along with a
tELTPostgresqlInput and tELTPostgresqlOutput. Note that the
Output link to be used with these components must correspond strictly to
the syntax of the table name.

Information noteNote:

Note that the ELT components do not
handle actual data flow but only schema information. | | 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
connection 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](https://help.qlik.com/talend/r/en-US/8.0/components/defining-context-groups/reading-data-from-databases-through-context-based-dynamic-connections) and [Reading data from different MySQL databases
using dynamically loaded connection parameters](https://help.qlik.com/talend/r/en-US/8.0/components/context/reading-data-from-different-mysql-databases-using-dynamically-loaded-connection-parameters). For more information on
Dynamic settings and context variables, see
[Dynamic schema](https://help.qlik.com/talend/r/en-US/8.0/studio-user-guide/dynamic-schema) and [Creating a context group and define context
variables in it](https://help.qlik.com/talend/r/en-US/8.0/studio-user-guide/creating-context-group-and-define-context-variables-in-it). |