PostgreSQL Replication Slots

The replication slot used here will be used in combination with pg_logical_slot_get_changes to consume each change of the slot (to compare with

The WAL files will just pile up So you need to monitor the slots and manually drop them Only when you do that will the master delete anything

bastian slot logical replication slots are still being used, you shouldn't delete them, and you can't proceed with the upgrade Cause Sign In To view full

slot treasure hunt Replication slots persist across crashes and know nothing about the state of their consumer They will prevent removal of required resources even when there