Thanks so much. That clarifies.
-Anupama
On Monday, April 14, 2014 12:09 PM, Michael Paquier
wrote:
On Sat, Apr 12, 2014 at 3:12 PM, Anupama Ramaswamy wrote:
> Lets suppose at this point there is 0 delivery lag but bytes of replay
> lag.
>
All your answers are here:
http://www.postgresql
On Sat, Apr 12, 2014 at 3:12 PM, Anupama Ramaswamy wrote:
> Lets suppose at this point there is 0 delivery lag but bytes of replay
> lag.
>
All your answers are here:
http://www.postgresql.org/docs/devel/static/warm-standby.html
"Standby mode is exited and the server switches to normal operat
Thanks for your response.
>>There are two lag types to consider about in case of a normal
>>streaming replication - delivery lag and replay lag. The secondary
>>will completely catch up to what have been delivered, but what have
>>not been is going to be lost. See [1][2].
Ok, I understand. I want
On Sat, Apr 5, 2014 at 3:48 AM, Anupama Ramaswamy wrote:
> Scenario 1
>
> Suppose the secondary server is lagging behind the primary at the time of
> primary failure, will the secondary completely catch up to the primary
> state, before stopping replication. Or what in the process
I have 2 postgres nodes setup in a replication and hot standby configuration. I
am using pgpool for automatic failover and load balancing the read queries.
I have setup scripts for automatic failover when the master node fails. I want
to understand how it would work in the following 2 scenarios.
