PostgreSQL CDC

The Micro-Integration for PostgreSQL CDC captures changes (inserts, updates, deletes) from a PostgreSQL database table (using Debezium) and streams them to a topic on an event broker service.

You can configure PostgreSQL only as a source.

To configure the connection details for PostgreSQL in your Micro-Integration, see PostgreSQL CDC Connection Parameters

You must also define at least one Micro-Integration Flow that specifies:

For message headers, see PostgreSQL CDC Message Headers.

PostgreSQL CDC Connection Parameters

The following table describes the connection parameters for PostgreSQL CDC.

Field Description
Checkpoint Queue The name of the Last Value Queue (LVQ) on the Solace event broker to use for checkpointing. The LVQ stores information about the files that have been processed and the files that are currently being processed. The LVQ must exist on the same event broker and VPN as the target destination.
Auto Create Checkpoint Queue Select to automatically create the LVQ if it does not exist. The default value is false.

Micro-Integration Flow Parameters

You must configure the endpoint parameters for each Flow. Each Flow can have different settings, but they all share the connection details of the parent Micro-Integration.

PostgreSQL CDC Source Parameters

The following table describes the parameters for configuring PostgreSQL CDC as a source.

Field Description
Destination The name of the table, including the schema name. Specify the destination using the <schemaName>.<tableName> format.
Database Hostname The hostname of the PostgreSQL database server.
Database Port The port of the PostgreSQL database server.
Database Name The name of the PostgreSQL database.
Slot Name

The name of the PostgreSQL logical decoding slot.

A logical decoding slot is a persistent object that maintains a stream of database changes. The Micro-Integration for PostgreSQL CDC consumes the change stream from the specified slot.
Skip Delete Events Select to skip the processing of delete events from the database change stream.
Authentication

The type of authentication to use when connecting to PostgreSQL. Choose one of:

Additional Properties

(Optional) Any additional configuration related to PostgreSQL. Click Add Context if you need to specify additional context properties.

Basic Authentication Parameters

Field Description
Username The username to use for logging in to PostgreSQL.
Password The password to use for authenticating with the PostgreSQL database.

Client Certificate Authentication Parameters

Field Description
Database SSL mode

The SSL mode determines the security level for client-server communications. It controls whether SSL/TLS encryption is used and how rigorously the server's identity is verified. Choose one of:

  • disable to use an unencrypted connection

  • allow to try to use an unencrypted connection first and, failing that, a secure (encrypted) connection

  • prefer to try to use a secure (encrypted) connection first and, failing that, an unencrypted connection

  • require to use a secure (encrypted) connection, and fail if one cannot be established

  • verify-ca like required but additionally verify the server TLS certificate against the configured Certificate Authority (CA) certificates, or fail if no valid matching CA certificates are found

  • verify-full like verify-ca but additionally verify that the server certificate matches the host to which the connection is attempted

For more information, see the Protection Provided in Different Modes section of the PostgreSQL documentation.
Client certificate The SSL Certificate for the client.
Client private key The SSL private key for the client.
Private key password The database SSL password to authenticate with the PostgreSQL database.
SSL Root Certificate The database SSL root certificate against which the server is validated.
Username The username to use for logging in to PostgreSQL.