Re: Need Force flag for pg_drop_replication_slot() - Mailing list pgsql-hackers

From Stephen Frost
Subject Re: Need Force flag for pg_drop_replication_slot()
Date
Msg-id 20150529183901.GE26667@tamriel.snowman.net
Whole thread Raw
In response to Re: Need Force flag for pg_drop_replication_slot()  (Andres Freund <andres@anarazel.de>)
Responses Re: Need Force flag for pg_drop_replication_slot()  (Andres Freund <andres@anarazel.de>)
List pgsql-hackers
* Andres Freund (andres@anarazel.de) wrote:
> How is this measurably worse than trying to truncate a log table that
> has grown too large? That's often harder to fight actually, because
> there's dozens of other processes that might be using the relation?  In
> one case you don't have wait ordering, but only one locker, in the other
> case you have multiple waiters, and to benefit from wait ordering you
> need multiple sessions.

Because we don't fall over if we can't extend a relation.

We do fall over if we can't write WAL.
Thanks!
    Stephen

pgsql-hackers by date:

Previous
From: Josh Berkus
Date:
Subject: Re: Need Force flag for pg_drop_replication_slot()
Next
From: Josh Berkus
Date:
Subject: Re: RFC: Remove contrib entirely