Postgres Pro
Downloads
Home   >   mailing lists

Re: A proposal to force-drop replication slots to make disabling async/sync standbys or logical replication faster in production environments - Mailing list pgsql-hackers

From Bharath Rupireddy
Subject Re: A proposal to force-drop replication slots to make disabling async/sync standbys or logical replication faster in production environments
Date
Msg-id CALj2ACWOXOk+zXU_1QBb1KBCOU-0YUcXD+ejUG-3YeaX=dMiXQ@mail.gmail.com
Whole thread Raw
In response to Re: A proposal to force-drop replication slots to make disabling async/sync standbys or logical replication faster in production environments  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
Tree view 
On Thu, Jun 9, 2022 at 11:24 AM Tom Lane <tgl@sss.pgh.pa.us> wrote:
>
> Bharath Rupireddy <bharath.rupireddyforpostgres@gmail.com> writes:
> > How about we provide a function to force-drop a replication slot?
>
> Isn't this akin to filing off the safety interlock on the loaded revolver
> you keep in your hip pocket?  IMO the entire point of replication slots
> is to not make it easy to lose data.

Agree. How about making the function superuser-only?

Regards,
Bharath Rupireddy.

pgsql-hackers by date:

Previous
From: Amit Kapila
Date:
Subject: Re: Multi-Master Logical Replication
Next
From: Bharath Rupireddy
Date:
Subject: Re: A proposal to force-drop replication slots to make disabling async/sync standbys or logical replication faster in production environments