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

From Bossart, Nathan
Subject Re: Postgres restart in the middle of exclusive backup and the presence of backup_label file
Date
Msg-id 845544A4-0B0E-41D2-903C-C8B9E8A18812@amazon.com
Whole thread Raw
In response to Re: Postgres restart in the middle of exclusive backup and the presence of backup_label file  (Stephen Frost <sfrost@snowman.net>)
Responses 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, 9:51 AM, "Stephen Frost" <sfrost@snowman.net> wrote:
> I disagree that that’s a satisfactory approach. It certainly wasn’t
> intended or documented as part of the original feature and therefore
> to call it satisfactory strikes me quite strongly as revisionist
> history. 

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.

Nathan


pgsql-hackers by date:

Previous
From: Bruce Momjian
Date:
Subject: Re: Correct handling of blank/commented lines in PSQL interactive-mode history
Next
From: Peter Smith
Date:
Subject: Re: row filtering for logical replication