Re: Postgres restart in the middle of exclusive backup and the presence of backup_label file
Nathan Bossart <bossartn@amazon.com>
From: "Bossart, Nathan" <bossartn@amazon.com>
To: Stephen Frost <sfrost@snowman.net>, Laurenz Albe <laurenz.albe@cybertec.at>
Cc: Michael Paquier <michael@paquier.xyz>, Pg Hackers <pgsql-hackers@postgresql.org>, SATYANARAYANA NARLAPURAM <satyanarlapuram@gmail.com>, Tom Lane <tgl@sss.pgh.pa.us>
Date: 2021-11-30T21:56:36Z
Lists: 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
Commits
-
Remove duplicated word in comment of basebackup.c
- 83cca409edf2 15.0 landed