pg_wal eat disk because inactive replication slot #2012

Don't drop the group slot Although usually inactive, it's still vital to the proper operation of the EDB Postgres Distributed cluster If you drop it, then

Replication slots were introduced with PostgreSQL and are designed to ensure that any standby connected to the primary using a replication slot will always

postgresql drop replication slot Starting from PostgreSQL , it is also necessary and useful to check for leftover replication slots The core issue is that if somebody forgets to drop a

postgresql create replication slot You can list all available replication slots and their details using the pg_replication_slots view SELECT * FROM pg_replication_slots;