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

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Bharath Rupireddy <bharath(dot)rupireddyforpostgres(at)gmail(dot)com>
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-09 05:54:57
Message-ID: 1872492.1654754097@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

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.

regards, tom lane

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Peter Geoghegan 2022-06-09 06:00:37 Re: Collation version tracking for macOS
Previous Message Michael Paquier 2022-06-09 05:47:36 Re: Bump MIN_WINNT to 0x0600 (Vista) as minimal runtime in 16~