Table of Contents

Search

PowerExchange for PostgreSQL User Guide for PowerCenter

PowerExchange for PostgreSQL User Guide for PowerCenter

Configure PostgreSQL Target Session Properties

Configure PostgreSQL Target Session Properties

You can configure the session properties for a PostgreSQL target on the
Workflow Manager
tab. Define the properties for the target instance in the session.
The following table describes the session properties that you can configure for a PostgreSQL target session:
Session Property
Description
Update Mode
Specifies the mode to write data to PostgreSQL target. You can specify the following modes:-
- Update As Update. Updates all rows flagged for update if the entries exist.
- Update Else Insert. Updates all rows flagged for update if the entries exist in the target. If the entries do not exist, the PowerCenter Integration Service inserts the entries.
Pre-SQL
The pre-SQL commands to run before the PowerCenter Integration Service writes data to the target.
You can use the pre-SQL query to call a stored procedure in a PostgreSQL database.
Post-SQL
The post-SQL commands to run after the PowerCenter Integration Service writes data to the target.
You can use the post-SQL query to call a stored procedure in a PostgreSQL database.
Truncate Target
The PowerCenter Integration Service truncates the target before writing the data.
Enable target bulk load
Performs bulk upload when you configure an insert operation to write to PostgreSQL. Select this option to improve the performance of inserting data in bulk to PostgreSQL.
Default is unselected.
When you enable the target bulk mode to insert data to PostgreSQL and stop on errors is set to a value greater than 0, the error files are not generated for rejected records.
Batch Size
The number of rows that the PowerCenter Integration Service writes in a single batch to PostgreSQL. Specify a batch size value that is greater than zero.
Default is 0.
Applicable if you select the
Enable target bulk load
option.
Schema Name
Optional. Overrides the schema name of the target object.
Ensure that the target table name and its metadata are identical. Otherwise, you might get an error that table does not exist under the specified overridden schema.

0 COMMENTS

We’d like to hear from you!