Re: Add recovery to pg_control and remove backup_label
Michael Paquier <michael@paquier.xyz>
From: Michael Paquier <michael@paquier.xyz>
To: Andres Freund <andres@anarazel.de>
Cc: Robert Haas <robertmhaas@gmail.com>, David Steele <david@pgmasters.net>, Postgres hackers <pgsql-hackers@lists.postgresql.org>
Date: 2023-11-21T03:45:55Z
Lists: pgsql-hackers
On Mon, Nov 20, 2023 at 03:58:55PM -0800, Andres Freund wrote: > I was thinking we'd just set it in the pg_basebackup style path, and we'd > error out if it's set and backup_label is present. But we'd still use > backup_label without the pg_control flag set. > > So it'd just provide a cross-check that backup_label was not removed for > pg_basebackup style backup, but wouldn't do anything for external backups. But > imo the proposal to just us pg_control doesn't actually do anything for > external backups either - which is why I think my proposal would achieve as > much, for a much lower price. I don't see why not. It does not increase the number of steps when doing a backup, and backupStartPoint alone would not be able to offer this much protection. -- Michael
Commits
-
Doc: improve documentation for jsonpath behavior.
- 7014c9a4bba2 17.0 cited
-
Extend sendFileWithContent() to handle custom content length in basebackup.c
- 7606175991f8 17.0 landed