Re: Add recovery to pg_control and remove backup_label
Andres Freund <andres@anarazel.de>
From: Andres Freund <andres@anarazel.de>
To: "David G. Johnston" <david.g.johnston@gmail.com>
Cc: Robert Haas <robertmhaas@gmail.com>, Michael Paquier <michael@paquier.xyz>, David Steele <david@pgmasters.net>, Postgres hackers <pgsql-hackers@lists.postgresql.org>
Date: 2023-11-20T23:41:40Z
Lists: pgsql-hackers
Hi, On 2023-11-20 14:18:15 -0700, David G. Johnston wrote: > On Mon, Nov 20, 2023 at 1:37 PM Andres Freund <andres@anarazel.de> wrote: > > > > > Given that, I wonder if what we should do is to just add a new field to > > pg_control that says "error out if backup_label does not exist", that we > > set > > when creating a streaming base backup > > > > > I thought this was DOA since we don't want to ever leave the cluster in a > state where a crash requires intervention to restart. I was trying to suggest that we'd set the field in-memory, when streaming out a pg_basebackup style backup (by just replacing pg_control with an otherwise identical file that has the flag set). So it'd not have any effect on the primary. Greetings, Andres Freund
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