From: Scott Ribe <scott_ribe@elevated-dev.com>
To: pgsql-admin <pgsql-admin@postgresql.org>
Subject: Re: HA Setup Review
Date: Tue, 30 Apr 2024 08:47:48 -0600
Message-ID: <DB252091-0D4D-45A1-BACB-7C521A018350@elevated-dev.com> (raw)
In-Reply-To: <CANzqJaBz8Of8DANUehyRC1KEniGUikp1KPk29DNhh66Vuhan5Q@mail.gmail.com>
References: <CAHecRenM5M9G3mmbE5srhUso0MFC-g6F5rVjwrXo_vZ7fvEt9Q@mail.gmail.com>
<CANzqJaBd1yhJxCr25iiTwnOstVo_TcZU5AHdv=s+zTEeOgjO=w@mail.gmail.com>
<PH0PR19MB5573B83EE17D1393CF88B6E5D61A2@PH0PR19MB5573.namprd19.prod.outlook.com>
<CANzqJaBz8Of8DANUehyRC1KEniGUikp1KPk29DNhh66Vuhan5Q@mail.gmail.com>
> On Apr 30, 2024, at 8:20 AM, Ron Johnson <ronljohnsonjr@gmail.com> wrote:
>
> ZERO downtime is -- to my knowledge -- impossible with master-slave replication. There will always be some seconds of lag while the secondary-that-was is promoted to new-primary, and the applications that were forcibly disconnected from the old primary are connected to the new-primary.
>
> Heck, even in a master-master DB cluster, any connections on the master that dies will be down until they can connect to the other master.
This is true. However, with a secondary that is up to date, and applications accessing through pgbouncer, client connections to pgbouncer are not broken, and pgbouncer connections to postgres can be reestablished quickly enough that users only observe a slightly slow response.
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-admin@postgresql.org
Cc: scott_ribe@elevated-dev.com
Subject: Re: HA Setup Review
In-Reply-To: <DB252091-0D4D-45A1-BACB-7C521A018350@elevated-dev.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox