From: | Stephen Frost <sfrost(at)snowman(dot)net> |
---|---|
To: | Paul Förster <paul(dot)foerster(at)gmail(dot)com> |
Cc: | James Sewell <james(dot)sewell(at)jirotech(dot)com>, "pgsql-generallists(dot)postgresql(dot)org" <pgsql-general(at)lists(dot)postgresql(dot)org> |
Subject: | Re: Safe switchover |
Date: | 2020-07-13 16:07:42 |
Message-ID: | 20200713160742.GW12375@tamriel.snowman.net |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
Greetings,
* Paul Förster (paul(dot)foerster(at)gmail(dot)com) wrote:
> > On 13. Jul, 2020, at 18:00, Stephen Frost <sfrost(at)snowman(dot)net> wrote:
> > Ah, yes, if you rebuild the replica from a backup (or from the primary),
> > then sure, that's pretty similar to the pgbackrest delta restore, except
> > that when using delta restore we're only rewriting files that have a
> > different SHA checksum after being scanned, and we're pulling from the
> > backup repo anything that's needed and not putting load on the primary.
>
> so, from what I understand, pgbackrest bottom line merely reduces copy overhead in such a particular case. *Kind of* like shutdown primary, rsync, and then startup.
Yes, though unlike rsync, pgbackrest can also run in parallel.. :)
> > There's been a few discussions on -hackers about this, that'd probably
> > be the place to discuss it further..
>
> I'm not hacker, I'm just a DBA. :-)
You're a PG user, so your input is (at least) as valuable regarding
things like this, imv. :)
Thanks!
Stephen
From | Date | Subject | |
---|---|---|---|
Next Message | Jehan-Guillaume de Rorthais | 2020-07-13 16:52:08 | Re: Safe switchover |
Previous Message | Paul Förster | 2020-07-13 16:05:59 | Re: Safe switchover |