Data Integrity Issues After Recreating a Replication Slot With the Same Name

Issue

Data integrity issues occur after dropping and recreating a replication slot with the same name.

Environment

Connector: PostgreSQL

Resolution

To resolve this issue, you must re-sync your connection. To learn how, see How to Trigger Historical Re-Syncs for Fivetran Connections.

Cause

When you drop and recreate a replication slot with the same name, the new slot doesn't have access to the WAL history generated before it was created and doesn't retain the previous Log Sequence Number (LSN). As a result, we can't read or sync updates that occurred before the new slot was created or while the slot was absent.