On Thu, Jun 9, 2022 at 11:07 AM Bharath Rupireddy <bharath.rupireddyforpostg...@gmail.com> wrote: > > Currently postgres doesn't allow dropping a replication slot that's active > [1]. This can make certain operations more time-consuming or stuck in > production environments. These operations are - disable async/sync standbys > and disable logical replication that require the postgres running on standby > or the subscriber to go down. If stopping postgres server takes time, the VM > or container will have to be killed forcefully which can take a considerable > amount of time as there are many layers in between. >
Why do you want to drop the slot when the server is going down? Is it some temporary replication slot, otherwise, how will you resume replication after restarting the server? -- With Regards, Amit Kapila.
