| From: | Paul Förster <paul(dot)foerster(at)gmail(dot)com> |
|---|---|
| To: | Michael Paquier <michael(at)paquier(dot)xyz> |
| Cc: | Curt Kolovson <curt(at)kolovson(dot)org>, pgsql-general(at)lists(dot)postgresql(dot)org |
| Subject: | Re: how reliable is pg_rewind? |
| Date: | 2020-08-03 05:29:10 |
| Message-ID: | 81E7842B-EE4F-40B9-AA87-F896379E3255@gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
Hi Curt, hi Michael,
> On 03. Aug, 2020, at 03:58, Michael Paquier <michael(at)paquier(dot)xyz> wrote:
>
> On Sat, Aug 01, 2020 at 10:35:37AM -0700, Curt Kolovson wrote:
>> Any info on the reliability of pg_rewind and its limitations would be appreciated.
>
> FWIW, we use it in production to accelerate the redeployment of
> standbys in HA configuration for 4 years now in at least one product,
> and it is present in upstream for since 9.5, for 5 years now. So the
> tool is rather baked at this stage of the game.
same here. We use it with Patroni in failover cluster setups for about 2-3 years now. It has not failed us yet.
Cheers,
Paul
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Curt Kolovson | 2020-08-03 06:25:06 | Re: how reliable is pg_rewind? |
| Previous Message | alex m | 2020-08-03 05:04:53 | How to get the name of the current database in C function/extention inside a trigger? |