| From: | "Bossart, Nathan" <bossartn(at)amazon(dot)com> |
|---|---|
| To: | David Steele <david(at)pgmasters(dot)net>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Stephen Frost <sfrost(at)snowman(dot)net>, Laurenz Albe <laurenz(dot)albe(at)cybertec(dot)at>, Michael Paquier <michael(at)paquier(dot)xyz>, Pg Hackers <pgsql-hackers(at)postgresql(dot)org>, SATYANARAYANA NARLAPURAM <satyanarlapuram(at)gmail(dot)com> |
| Subject: | Re: Postgres restart in the middle of exclusive backup and the presence of backup_label file |
| Date: | 2021-11-30 23:31:04 |
| Message-ID: | BC31E8F0-7CFF-462E-9B27-727AD573A675@amazon.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 11/30/21, 2:58 PM, "David Steele" <david(at)pgmasters(dot)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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Peter Geoghegan | 2021-12-01 00:21:25 | Deprecating the term "super-exclusive lock" |
| Previous Message | David Steele | 2021-11-30 22:58:15 | Re: Postgres restart in the middle of exclusive backup and the presence of backup_label file |