# tPostgresqlCDC Standard properties These properties are used to configure tPostgresqlCDC running in the Standard Job framework. The Standard tPostgresqlCDC component belongs to the Databases family. The component in this framework is available in all Talend products. Information noteNote: 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](https://help.qlik.com/talend/r/en-US/7.3/components/db-generic/dynamic-database-components). ## Basic settings | Database | Select a type of database from the list and click
Apply. | | --- | --- | | Property type | Either Built-in or
Repository | | | Built-in: No property data stored
centrally. | | | Repository: Select the repository
file in which the properties are stored. The fields that follow are
completed automatically using the data retrieved.

Information noteWarning:


*Reset the DB type by clicking the relevant button to
select the CDC connection.* | | 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, 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 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 *Talend Studio
User Guide*. | | DB Version | List of database versions. | | Host | Database server IP address. | | Port | DB server listening port number. | | Database | Name of the database. | | Schema | Name of the schema. | | Username and
Password | 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. | | Schema using CDC and Edit
Schema | 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
schema to make changes to the schema. If the current schema is of the Repository type, three options are available:

| | | Built-In: You create and store the schema locally for this component
only. | | | Repository: You have already created the schema and stored it in the
Repository. You can reuse it in various projects and Job designs.

Information noteWarning:


*Reset the DB type by clicking the relevant button to
select the schema of the CDC connection.* | | Table | Select the source table from which any changes made to data are to
be captured. | | Subscriber | Enter the name of the application that will use the change
table. | | Events to catch | Insert: Select this check box to
catch the data inserted in the change table since the last
extracion.


Update: Select this check box to
catch the data updated in the change table since the last
extracion.


Delete: Select this check box to
catch the data deleted in the change table since the last
extracion. | ## 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. | | --- | --- | | Keep data in CDC Table | Select this check box to keep the changes made available to one or
more target systems, even after they have been consulted. | | Use cursor | Select this check box to specify the number of rows you want to
work with at at any given time. This option optimises
performance. | | Trim all the String/Char columns | Select this check box to delete any spaces found at the beginning
or end of fields, in all of the columns containing character
strings. | | Trim column | Remove leading and trailing whitespace from defined
columns.

Information noteNote:

Clear Trim all the String/Char
columns to enable Trim columns in this
field. | | tStatCatcher Statistics | Select this check box to collect the log data at component
level. | | 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
variables to retrieve return values in a subJob.

| ## Global Variables | Global Variables | NB\_LINE: the number
of rows read by an input component or transferred to an output component. This is an
After variable and it returns an integer.

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 further information about variables, see *Talend Studio*
*User Guide*.

A Flow variable functions during the execution of a component
while an After variable functions after the execution of the component. | | --- | --- | ## Usage | **Usage rule** | This component is used as a start component. It requires an output
component and a row Main link. | | --- | --- |