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 Tom Lane
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 1872492.1654754097@sss.pgh.pa.us
Whole thread Raw
In response to A proposal to force-drop replication slots to make disabling async/sync standbys or logical replication faster in production environments  (Bharath Rupireddy <bharath.rupireddyforpostgres@gmail.com>)
Responses Re: A proposal to force-drop replication slots to make disabling async/sync standbys or logical replication faster in production environments
List pgsql-hackers
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.

            regards, tom lane



pgsql-hackers by date:

Previous
From: Michael Paquier
Date:
Subject: Re: Bump MIN_WINNT to 0x0600 (Vista) as minimal runtime in 16~
Next
From: Peter Geoghegan
Date:
Subject: Re: Collation version tracking for macOS