| From: | Andreas Kretschmer <andreas(at)a-kretschmer(dot)de> |
|---|---|
| To: | pgsql-general(at)lists(dot)postgresql(dot)org |
| Subject: | Re: Operating of synchronous master when no standby is available |
| Date: | 2023-10-02 11:15:18 |
| Message-ID: | 78ff6888-006e-cdba-8d77-9d6b5678fab2@a-kretschmer.de |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
Am 02.10.23 um 10:54 schrieb Sergey Cherukhin:
> Hello!
>
> I use Postgresql+Pacemaker+Corosync cluster with 2 Postgresql
> instances in synchronous replication mode. When one of the nodes is
> down, clients hang on INSERT operations because the primary server
> waits until standby confirms that it got the data, but the standby
> node is down.
>
> I need clients to feel no difference when they operate with a fully
> operational cluster or with a degraded cluster containing primary
> node alone.
>
> Is it possible to configure synchronous replication to operate
> normally when primary and replica are online, but primary no waits
> confirmation from replica if replica is not connected?
yes, with 3 or more sync. standbys.
Andreas
--
Andreas Kretschmer
Technical Account Manager (TAM)
www.enterprisedb.com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Matthias Apitz | 2023-10-02 11:27:42 | How to investigate deadlocks |
| Previous Message | Sergey Cherukhin | 2023-10-02 08:54:30 | Operating of synchronous master when no standby is available |