On Tue, Oct 17, 2023 at 12:30 PM David Steele wrote:
> On 10/17/23 14:28, Robert Haas wrote:
> > On Mon, Oct 16, 2023 at 5:21 PM David G. Johnston
> > wrote:
> >> But no, by default, and probably so far as pg_basebackup is concerned,
> a server crash during backup results in requiring outside
On 10/17/23 14:28, Robert Haas wrote:
On Mon, Oct 16, 2023 at 5:21 PM David G. Johnston
wrote:
But no, by default, and probably so far as pg_basebackup is concerned, a server
crash during backup results in requiring outside intervention in order to get
the server to restart.
Others may
On Mon, Oct 16, 2023 at 5:21 PM David G. Johnston
wrote:
> But no, by default, and probably so far as pg_basebackup is concerned, a
> server crash during backup results in requiring outside intervention in order
> to get the server to restart.
Others may differ, but I think such a proposal is
On Mon, Oct 16, 2023 at 12:36 PM David G. Johnston <
david.g.johns...@gmail.com> wrote:
> On Mon, Oct 16, 2023 at 12:09 PM Laurenz Albe
> wrote:
>
>> I think it won't meet with favor if there are cases that require manual
>> intervention
>> for starting the server. That was the main argument
On Mon, Oct 16, 2023 at 12:09 PM Laurenz Albe
wrote:
> I think it won't meet with favor if there are cases that require manual
> intervention
> for starting the server. That was the main argument for getting rid of
> the exclusive
> backup API, which had a similar problem.
>
In the rare case
On Mon, 2023-10-16 at 11:18 -0700, David G. Johnston wrote:
> > I see a couple of problems and/or things that need clarification with that
> > idea:
> >
> > - Two backups can run concurrently. How do you reconcile that with the "in
> > backup"
> > flag and crash.signal?
> > - I guess
On Mon, Oct 16, 2023 at 10:26 AM Laurenz Albe
wrote:
> On Mon, 2023-10-16 at 09:26 -0700, David G. Johnston wrote:
> > This email is a first pass at a user-visible design for how our backup
> and restore
> > process, as enabled by the Low Level API, can be modified to make it
> more
On Mon, 2023-10-16 at 09:26 -0700, David G. Johnston wrote:
> This email is a first pass at a user-visible design for how our backup and
> restore
> process, as enabled by the Low Level API, can be modified to make it more
> mistake-proof.
> In short, it requires pg_start_backup to further
Hi!
This email is a first pass at a user-visible design for how our backup and
restore process, as enabled by the Low Level API, can be modified to make
it more mistake-proof. In short, it requires pg_start_backup to further
expand upon what it means for the system to be in the midst of a
