| From: | MATSUO Takatoshi <matsuo(dot)tak(at)gmail(dot)com> |
|---|---|
| To: | Sergey Cherukhin <sergey(dot)cherukhin(at)gmail(dot)com> |
| Cc: | pgsql-general(at)lists(dot)postgresql(dot)org |
| Subject: | Re: Operating of synchronous master when no standby is available |
| Date: | 2023-10-02 22:13:03 |
| Message-ID: | CAKwUP094nw4-aydGFK5ojYYM+n4i+1RhWAUA2wi+4BV-rA5Anw@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
Pgsql RA has rep_mode=sync parameter.
https://wiki.clusterlabs.org/wiki/PgSQL_Replicated_Cluster
2023年10月2日(月) 23:48 Sergey Cherukhin <sergey(dot)cherukhin(at)gmail(dot)com>:
> 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 | David G. Johnston | 2023-10-02 22:25:02 | Re: How to investigate deadlocks |
| Previous Message | Karl O. Pinc | 2023-10-02 19:23:00 | Re: Trigger functions and parallelism |