Openflow Connector for PostgreSQL Maintenance¶

Upgrading PostgreSQL¶

Upgrading the connector requires a different approach depending on whether PostgreSQL is being upgraded to the next minor or major version.

Minor version upgrades

• Are data safe.

• Require no special treatment.

• Require stopping the connector for the duration of the upgrade to avoid reporting connectivity issues.

• Continue replicating, after the upgrade, with no data loss.

Major version upgrades

• Require the PostgreSQL server to drop replication slots, including any used by the connector.

• Cannot preserve, or migrate replication slots to the new version. See also PostgresSQL 17 and later versions upgrades.

• Restart replicating all tables from the prior snapshot phase.

To perform a minor version upgrade, do the following:

1. Stop the connector, including all Processors and Controller Services.

2. Upgrade PostgreSQL.

3. Restart the connector.

To perform a major version upgrade, do the following:

1. Remove all tables from replication in the connector.

2. Wait until all queues in the connector are empty.

3. Stop the connector, including all Processors and Controller Services.

4. Open the Incremental Load group in the connector.

5. Right-click the top Processor in the group, Read PostgreSQL CDC Stream, and select View state.

6. Click Clear state.

7. Click Close.

8. Upgrade PostgreSQL.

9. Restart the connector. A new replication slot will be created.

10. Re-add all tables to begin replication.

PostgresSQL 17 and later versions upgrades¶

PostgreSQL 17 improved upgrading such that it no longer requires dropping replication slots when upgrading to later versions such as 17.1 » 17.0. Upgrading to PostgreSQL 17.0 or later from prior versions (16 and earlier) drops replications slots and should be treated as a major upgrade. Future versions of PostgreSQL may also improve the upgrade process further.