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

From Tom Lane
Subject Re: Postgres restart in the middle of exclusive backup and the presence of backup_label file
Date
Msg-id 1661037.1638311167@sss.pgh.pa.us
Whole thread Raw
In response to Re: Postgres restart in the middle of exclusive backup and the presence of backup_label file  ("Bossart, Nathan" <bossartn@amazon.com>)
Responses Re: Postgres restart in the middle of exclusive backup and the presence of backup_label file  ("Bossart, Nathan" <bossartn@amazon.com>)
Re: Postgres restart in the middle of exclusive backup and the presence of backup_label file  (David Steele <david@pgmasters.net>)
Re: Postgres restart in the middle of exclusive backup and the presence of backup_label file  (Andrew Dunstan <andrew@dunslane.net>)
List pgsql-hackers
"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.

            regards, tom lane



pgsql-hackers by date:

Previous
From: Peter Smith
Date:
Subject: Re: row filtering for logical replication
Next
From: "Bossart, Nathan"
Date:
Subject: Re: Postgres restart in the middle of exclusive backup and the presence of backup_label file