Re: Postgres restart in the middle of exclusive backup and the presence of backup_label file - Mailing list pgsql-hackers

From Andrew Dunstan
Subject Re: Postgres restart in the middle of exclusive backup and the presence of backup_label file
Date
Msg-id 979c5a50-4da3-4cd0-010e-7d17e6ebd69b@dunslane.net
Whole thread Raw
In response to Re: Postgres restart in the middle of exclusive backup and the presence of backup_label file  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
On 11/30/21 17:26, Tom Lane wrote:
> "Bossart, Nathan" <bossartn@amazon.com> writes:
>> It looks like the exclusive way has been marked deprecated in all
>> supported versions along with a note that it will eventually be
>> removed.  If it's not going to be removed out of fear of breaking
>> backward compatibility, I think the documentation should be updated to
>> say that.  However, unless there is something that is preventing users
>> from switching to the non-exclusive approach, I think it is reasonable
>> to begin thinking about removing it.
> If we're willing to outright remove it, I don't have any great objection.
> My original two cents was that we shouldn't put effort into improving it;
> but removing it isn't that.
>
>             


+1


Let's just remove it. We already know it's a footgun, and there's been
plenty of warning.


cheers


andrew


--
Andrew Dunstan
EDB: https://www.enterprisedb.com




pgsql-hackers by date:

Previous
From: David Steele
Date:
Subject: Re: Postgres restart in the middle of exclusive backup and the presence of backup_label file
Next
From: Alvaro Herrera
Date:
Subject: Re: Is it worth adding ReplicationSlot active_pid to ReplicationSlotPersistentData?