Set up logical replication to Aiven for PostgreSQL

After deleting the unused replication slot, PGSQL happily goes about its business and purgesrotates the old, unnecessary WAL files If you

Set up logical replication to Aiven for PostgreSQL Typically, such replication slots are no longer active , because the standby server no longer connects to the primary Use the function pg_drop_replication_slot

After deleting the unused replication slot, PGSQL happily goes about its business and purgesrotates the old, unnecessary WAL files If you

postgresql drop 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

postgresql_slot module

postgresql replication slot 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

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