Use logical replication for tables in RDS for PostgreSQL

There are two options to fix this issue, either we can remove the used replication slots or increase the max_replication_slots parameter value

Use logical replication for tables in RDS for PostgreSQL Replication slots were introduced with PostgreSQL and are designed to ensure that any standby connected to the primary using a replication slot will always

There are two options to fix this issue, either we can remove the used replication slots or increase the max_replication_slots parameter value

drops of water slot Use pg_drop_replication_slot : select pg_drop_replication_slot; See the docs and this blog The replication slot must be

The core issue is that if somebody forgets to drop a replication slot, XLOG can accumulate, just as it does in the case of broken archive commands Therefore,

drop and lock slot machine Replication slots were introduced in PostgreSQL to help ensure a primary PostgreSQL instance does not remove WAL files before a replica has

A limitation of the PostgreSQL implementation is that replication slots are not cluster-aware: a replication slot exists solely on the instance