Replication Slot size increasing rapidly for postgresql

Replication Slot size increasing rapidly for postgresql delete replication slot postgres PostgreSQL will not remove transaction log files for which changes exist that have not been processed by a replication slot For this reason, replication slots microgame slot postgresql_slot module

microgame slot Now a common cause for this kind of issue are replication slots which are not advanced: in that case, Postgres will hold on to all WAL segments

sultan89 slot We were able to successfully stop the PID on the primary and then drop the replication slot using SELECT pg_drop_replication_slot If you stop syncing a CDC-configured Postgres instance with Airbyte, delete the replication slot Otherwise, it may fill up your disk space Supported