Re: Postgres restart in the middle of exclusive backup and the presence of backup_label file

From: Nathan Bossart <nathandbossart(at)gmail(dot)com>
To: Stephen Frost <sfrost(at)snowman(dot)net>
Cc: Chapman Flack <chap(at)anastigmatix(dot)net>, David Steele <david(at)pgmasters(dot)net>, pgsql-hackers(at)lists(dot)postgresql(dot)org
Subject: Re: Postgres restart in the middle of exclusive backup and the presence of backup_label file
Date: 2022-03-02 01:03:02
Message-ID: 20220302010302.GA1182956@nathanxps13
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Here is a new version of the patch with the following changes:

1. Addressed Chap's feedback from upthread.
2. Renamed pg_start/stop_backup() to pg_backup_start/stop() as
suggested by David.
3. A couple of other small documentation adjustments.

--
Nathan Bossart
Amazon Web Services: https://aws.amazon.com

Attachment Content-Type Size
v4-0001-remove-exclusive-backup-mode.patch text/x-diff 84.5 KB

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Robert Haas 2022-03-02 01:11:24 Re: Condition pushdown: why (=) is pushed down into join, but BETWEEN or >= is not?
Previous Message Noboru Saito 2022-03-02 00:57:21 Re: Separate the result of \watch for each query execution (psql)