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

From: Bharath Rupireddy <bharath(dot)rupireddyforpostgres(at)gmail(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>
Subject: Re: A proposal to force-drop replication slots to make disabling async/sync standbys or logical replication faster in production environments
Date: 2022-06-10 10:02:56
Message-ID: CALj2ACWOXOk+zXU_1QBb1KBCOU-0YUcXD+ejUG-3YeaX=dMiXQ@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Thu, Jun 9, 2022 at 11:24 AM Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
>
> Bharath Rupireddy <bharath(dot)rupireddyforpostgres(at)gmail(dot)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.

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Bharath Rupireddy 2022-06-10 10:03:27 Re: A proposal to force-drop replication slots to make disabling async/sync standbys or logical replication faster in production environments
Previous Message Amit Kapila 2022-06-10 09:29:57 Re: Multi-Master Logical Replication