Skip site navigation (1) Skip section navigation (2)

PG synchronous replication and unresponsive slave

From: Manoj Govindassamy <manoj(at)nimblestorage(dot)com>
To: <pgsql-general(at)postgresql(dot)org>, <pgsql-admin(at)postgresql(dot)org>
Subject: PG synchronous replication and unresponsive slave
Date: 2012-01-16 18:51:23
Message-ID: (view raw, whole thread or download thread mbox)
Lists: pgsql-adminpgsql-general
anyone with PG Synchronous Replication knowledge, please help me with 
your views on the below questions.


On 01/12/2012 10:12 AM, Manoj Govindassamy wrote:
> any help on this is much appreciated.
> thanks,
> Manoj
> On 01/11/2012 01:50 PM, Manoj Govindassamy wrote:
>> Hi,
>> I have a PG 9.1.2 Master <--> Slave with synchronous replication 
>> setup. They are all working fine as expected. I do have a case where 
>> I want to flip Master to non replication mode whenever its slave is 
>> not responding. I have set replication_timeout to 5s and whenever 
>> salve is not responding for for more than 5s, i see the master 
>> detecting it. But, the transactions on the master is stuck till the 
>> slave comes back. To get over it, I reloaded the config on master 
>> with synchronous_commit = local. Further transactions on the master 
>> are going thru fine with this local commits turned on.
>> Here are my questions:
>> 1. Transaction which was stuck right when slave going away never went 
>> thru even after I reloaded master's config with local commit on. I do 
>> see all new transactions on master are going thru fine, except the 
>> one which was stuck initially. How to get this stuck transaction 
>> complete or return with error.
>> 2. Whenever there is a problem with slave, I have to manually reload 
>> master's config with local commit turned on to get master go forward. 
>> Is there any automated way to reload this config with local commit on 
>> on slave's unresponsiveness ? tcp connection timeouts, replication 
>> timeouts all detect the failures, but i want to run some corrective 
>> action on these failure detection.

In response to


pgsql-admin by date

Next:From: David M. GulleverDate: 2012-01-16 20:24:41
Subject: apt installation postgresql 8.3
Previous:From: Frank LanitzDate: 2012-01-16 14:41:29
Subject: LDAP vs. local users

pgsql-general by date

Next:From: Heine FerreiraDate: 2012-01-16 20:15:25
Subject: can't find data type CIText or CI_Text
Previous:From: Tom LaneDate: 2012-01-16 18:11:36
Subject: Re: Problem with pgAgent on Ubuntu

Privacy Policy | About PostgreSQL
Copyright © 1996-2017 The PostgreSQL Global Development Group