A Guide to Logical Replication and CDC in PostgreSQL

A replication slot is created on the primary database server for each standby server The slot keeps track of the last confirmed receive location of WAL data on

Take Away The morale of the story? Don't leave your replication slots unattended! There shouldn't be any slots which are inactive for too long

replication slot is active for pid Inactive replication slots cause the accumulation of WAL files on the source DB instances WAL files might fill storage and cause outages Drop the subscription

replication slot The slot to be dropped must be inactive before it can be removed It is not possible to forcibly drop an active replication slot Change history PostgreSQL