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 BC31E8F0-7CFF-462E-9B27-727AD573A675@amazon.com
Whole thread Raw
In response to Re: Postgres restart in the middle of exclusive backup and the presence of backup_label file  (David Steele <david@pgmasters.net>)
Responses Re: Postgres restart in the middle of exclusive backup and the presence of backup_label file
List pgsql-hackers
On 11/30/21, 2:58 PM, "David Steele" <david@pgmasters.net> wrote:
> I did figure out how to keep the safe part of exclusive backup (not
> having to maintain a connection) while removing the dangerous part
> (writing backup_label into PGDATA), but it was a substantial amount of
> work and I felt that it had little chance of being committed.

Do you think it's still worth trying to make it safe, or do you think
we should just remove exclusive mode completely?

> Attaching the thread [1] that I started with a patch to remove exclusive
> backup for reference.

Ah, good, some light reading.  :)

Nathan


pgsql-hackers by date:

Previous
From: David Steele
Date:
Subject: Re: Postgres restart in the middle of exclusive backup and the presence of backup_label file
Next
From: Peter Geoghegan
Date:
Subject: Deprecating the term "super-exclusive lock"