Using PostgreSQL logical replication with Multi-AZ DB clusters

Confirm that the connector has created a new replication slot and that it is in active state by querying the pg_replication_slots table Resume the write

Using PostgreSQL logical replication with Multi-AZ DB clusters No more configuration is needed on the secondary server Finally, we created a replication slot What is the purpose of a replication slot in PostgreSQL?

Confirm that the connector has created a new replication slot and that it is in active state by querying the pg_replication_slots table Resume the write

replication slot This command shows information about logical replication slots that are setup on the database It shows if the slot is active, the state of the WAL sender

In this case the slot is called pg_basebackup_N where N is the PID of the backend process running the replication connection However there

replication slot postgres Although when a connector is not active, Postgres may allow other connector to consume the replication slot

To resolve these errors, remove the used replication slots, or increase the value of the max_replication_slots parameter Resolution Remove used replication