From: | Laura Smith <n5d9xq3ti233xiyif2vp(at)protonmail(dot)ch> |
---|---|
To: | "pgsql-general(at)lists(dot)postgresql(dot)org" <pgsql-general(at)lists(dot)postgresql(dot)org> |
Subject: | Re: Postgresql HA cluster |
Date: | 2023-10-13 19:21:46 |
Message-ID: | vpcXDAHFD1W7p676FE7rDkNf1qbvanrr7fAiULGOG0WmbUPQ2ZrlnOxgO7QTG8NB6m9fuGuP8o_Mm-9eduG7xjxeotEM-6KC2d0E9Mzxfk8=@protonmail.ch |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
------- Original Message -------
On Friday, October 13th, 2023 at 14:10, Jehan-Guillaume de Rorthais <jgdr(at)dalibo(dot)com> wrote:
> But really, double check first why a simple primary-standby architecture doesn't
> meet your needs. The simpler the architecture is, the better. Even from the
> application point of view.
>
From my perspective I do wonder why Postgres doesn't have an equivalent to MySQL Group Replication.
Although you can run MySQL GR as multi-primary, most people run it as primary-standby.
However the difference with Postgres is that MySQL Group does leader election. Whilst Postgres failover/failback is a highly manual affair.
From | Date | Subject | |
---|---|---|---|
Next Message | Pavel Luzanov | 2023-10-13 20:54:20 | Re: psql \du no more showing "member of" column |
Previous Message | Lele Gaifax | 2023-10-13 15:45:35 | Re: psql \du no more showing "member of" column |