From: | cen <cen(dot)is(dot)imba(at)gmail(dot)com> |
---|---|
To: | Inzamam Shafiq <inzamam(dot)shafiq(at)hotmail(dot)com> |
Cc: | "pgsql-general(at)lists(dot)postgresql(dot)org" <pgsql-general(at)lists(dot)postgresql(dot)org> |
Subject: | Re: Patroni vs pgpool II |
Date: | 2023-04-04 13:40:44 |
Message-ID: | 3a4d8c1c-c703-4eb3-a442-cb9f40796b2d@gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
> Can someone please suggest what is one (Patroni vs PGPool II) is best
> for achieving HA/Auto failover, Load balancing for DB servers. Along
> with this, can you please share the company/client names using these
> tools for large PG databases?
Having used pgpool in multiple production deployments I swore to never
use it again, ever.
The first reason is that you need a doctorate degree to try to
understand how it actually works, what the pcp commands do in each
scenario and how to correctly write the failover scripts.
It is basically a daemon glued together with scripts for which you are
entirely responsible for. Any small mistake in failover scripts and
cluster enters a broken state.
Even once you have it set up as it should, yes, it will fail over
correctly but it won't autoheal without manual intervention.
You also often end up in weird situation when backends are up, pgpool
reports down and similar scenarios and then you need to run the precise
sequence of pcp commands to recover
or destroy your whole cluster in the process if you mistype.
I haven't used patroni yet but it surely can't be worse.
Best regards, cen
From | Date | Subject | |
---|---|---|---|
Next Message | Adrian Klaver | 2023-04-04 15:12:52 | Re: jsonb @@ jsonpath operator doc: Only the first item of the result is taken into account |
Previous Message | Jehan-Guillaume de Rorthais | 2023-04-04 12:25:58 | Re: Patroni vs pgpool II |