Re: [ADMIN] How to Identify and Fail Transaction When Slave Node Down

Поиск
Список
Период
Сортировка
От Anushka Weerakkodyge
Тема Re: [ADMIN] How to Identify and Fail Transaction When Slave Node Down
Дата
Msg-id CAMsriHZ8Sd6N3Heq_TagiFP_sOFfMkbRgkkY4foZ3TJSNH10Hw@mail.gmail.com
обсуждение исходный текст
Ответ на [ADMIN] How to Identify and Fail Transaction When Slave Node Down  (Anushka Weerakkodyge <anushkaw@ceylonit.com>)
Ответы Re: [ADMIN] How to Identify and Fail Transaction When Slave Node Down  (vinny <vinny@xs4all.nl>)
Список 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 по дате отправления:

Предыдущее
От: Anushka Weerakkodyge
Дата:
Сообщение: [ADMIN] How to Identify and Fail Transaction When Slave Node Down
Следующее
От: vinny
Дата:
Сообщение: Re: [ADMIN] How to Identify and Fail Transaction When Slave Node Down