| From: | Sergey Cherukhin <sergey(dot)cherukhin(at)gmail(dot)com> |
|---|---|
| To: | pgsql-general(at)lists(dot)postgresql(dot)org |
| Subject: | Operating of synchronous master when no standby is available |
| Date: | 2023-10-02 08:54:30 |
| Message-ID: | CABVQyeqYocamAL0y7eLPdYP-q96U4e-Kd+uPwro-hDgPa56y4Q@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
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?
Best regards,
Sergey Cherukhin
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andreas Kretschmer | 2023-10-02 11:15:18 | Re: Operating of synchronous master when no standby is available |
| Previous Message | Giovanni Biscontini | 2023-10-02 07:50:24 | Re: pg_agent jobs |