From: | Sergey Cherukhin <sergey(dot)cherukhin(at)gmail(dot)com> |
---|---|
To: | pgsql-general(at)lists(dot)postgresql(dot)org |
Subject: | Re: Operating of synchronous master when no standby is available |
Date: | 2023-10-03 08:51:16 |
Message-ID: | CABVQyerM91C60WhFjJZOW7-FchxHWpL9==YFQ3HOs_=RgtLPHA@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
I already have rep_mode set to "sync", but the primary node switches to
async mode only if the replica is shutted down correctly. When I shut down
the replica by powering it off to emulate power unit failure, primary
remains in sync mode until "pcs resource cleanup" is performed. I think it
is possible to run resource cleanup in script on cluster alert.
вт, 3 окт. 2023 г. в 05:13, MATSUO Takatoshi <matsuo(dot)tak(at)gmail(dot)com>:
> 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 | Laurenz Albe | 2023-10-03 08:54:17 | Re: pg_stat_statements IN problem |
Previous Message | David Rowley | 2023-10-03 08:22:55 | Re: pg_stat_statements IN problem |