From: | Anushka Weerakkodyge <anushkaw(at)ceylonit(dot)com> |
---|---|
To: | pgsql-admin(at)postgresql(dot)org |
Subject: | Re: How to Identify and Fail Transaction When Slave Node Down |
Date: | 2017-03-16 09:06:19 |
Message-ID: | CAMsriHZ8Sd6N3Heq_TagiFP_sOFfMkbRgkkY4foZ3TJSNH10Hw@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-admin |
Hi,
problem still persists.
Is there any configuration (parameter?) to set the timeout of the
connection ? Because if the slave node is down, transaction to master node
waits forever until slave node comes back online.
Any suggestion would be highly appreciated.
Thanks,
Anushka
On Thu, Mar 16, 2017 at 5:21 AM, Anushka Weerakkodyge <anushkaw(at)ceylonit(dot)com
> wrote:
> Hi all,
>
> I have a synchronous streaming replication environment which is
> implemented using inbuilt replication mechanism in postgresql. Replication
> is working fine except I need to fail the data modification transactions
> when the slave node is not accessible.
>
> Is it possible?
>
> Please let me know whether there is a way to identify slave node status
> and fail the transaction using any inbuilt mechanism or some other
> technique.
>
> Thanks,
> Anushka
>
From | Date | Subject | |
---|---|---|---|
Next Message | vinny | 2017-03-16 09:51:37 | Re: How to Identify and Fail Transaction When Slave Node Down |
Previous Message | Anushka Weerakkodyge | 2017-03-15 23:51:23 | How to Identify and Fail Transaction When Slave Node Down |