Postgres WAL Overflow without Replication volumes -

When Kafka Connect attempts to restart the connector too quickly, the database sees that the slot is still active although the client has disconnected Hope

The root of the problem is that the Logical Replication Slot which exists on the primary is not available in a physical standby Meanwhile

replication slot already exists If the logical slot already exists, copy state information into the replication slots structure stored in the class instance Parameters: slots

replication slot does not exist Replication slot in PostgreSQL views · 2 years ago PostgreSQL Administration : Full course