Greetings,
* Paul Förster (paul.foerster@gmail.com) wrote:
> > On 21. Jun, 2020, at 21:35, Magnus Hagander <magnus@hagander.net> wrote:
> > One not uncommon case is for example being able to provision a new replica while a backup is running. Since
replicasare provisioned starting off a base backup, being able to run that concurrently is very useful. Especially if
basebackups take a long time to run.
>
> hmm, a backup shouldn't take so long as to delay a base backup significantly. But that's just my opinion. I may be a
littlesnapshot biased, though, where it only takes a few seconds. :-)
That's not the only case that I, at least, have heard of- folks aren't
really very happy with their backups fail when they could have just as
well completed, even if they're overlapping. Sure, it's better if
backups are scheduled such that they don't overlap, but that can be hard
to guarantee.
The thing about this is though that the new API avoids *other* issues,
like what happens if the system crashes during a backup (which is an
entirely common thing that happens, considering how long many backups
take...) and it does so in a relatively reasonable way while also
allowing concurrent backups, which is perhaps a relatively modest
benefit but isn't the main point of the different API.
Thanks,
Stephen
