A proposal to force-drop replication slots to make disabling async

A physical replication slot prevents a source DB instance from removing WAL data before it's consumed by all read replicas Each read replica has its own

Drop the replication slot created on the incorrect database An unused slot will continue to hold on to the Write Ahead Log forever which can cause server bloat

postgresql replication slot A physical replication slot prevents a source DB instance from removing WAL data before it's consumed by all read replicas Each read replica has its own

postgresql drop replication slot > > Currently postgres doesn't allow dropping a replication slot that's active This can make certain operations more time-consuming or