| 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-10 15:29:59 |
| Message-ID: | 20200710152959.GK12375@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:
> I wouldn't work out the procedure myself, especially since there is a free working solution already. It's dangerous if you do it yourself and make a mistake.
>
> In our company, we rely on Patroni (https://github.com/zalando/patroni) Yes, it uses pg_rewind in the background but it does switchover and failover fast and reliably (also for high load databases), handles timelines automatically and so on.
Patroni also has the option to use pgbackrest instead of pg_rewind.
Thanks,
Stephen
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Paul Förster | 2020-07-10 15:31:47 | Re: Safe switchover |
| Previous Message | Adrian Klaver | 2020-07-10 15:10:43 | Re: invalid non-zero objectSubId for object class |