Re: [ADMIN] How to Identify and Fail Transaction When Slave Node Down - Mailing list pgsql-admin

From Anushka Weerakkodyge
Subject Re: [ADMIN] How to Identify and Fail Transaction When Slave Node Down
Date
Msg-id CAMsriHZ8Sd6N3Heq_TagiFP_sOFfMkbRgkkY4foZ3TJSNH10Hw@mail.gmail.com
Whole thread Raw
In response to [ADMIN] How to Identify and Fail Transaction When Slave Node Down  (Anushka Weerakkodyge <anushkaw@ceylonit.com>)
Responses Re: [ADMIN] How to Identify and Fail Transaction When Slave Node Down
List 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@ceylonit.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

pgsql-admin by date:

Previous
From: Anushka Weerakkodyge
Date:
Subject: [ADMIN] How to Identify and Fail Transaction When Slave Node Down
Next
From: vinny
Date:
Subject: Re: [ADMIN] How to Identify and Fail Transaction When Slave Node Down