Re: Slave enters in recovery and promotes when WAL stream with master is cut + delay master/slave

From: Heikki Linnakangas <hlinnakangas(at)vmware(dot)com>
To: Andres Freund <andres(at)2ndquadrant(dot)com>
Cc: Michael Paquier <michael(dot)paquier(at)gmail(dot)com>, Alvaro Herrera <alvherre(at)2ndquadrant(dot)com>, PostgreSQL mailing lists <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Slave enters in recovery and promotes when WAL stream with master is cut + delay master/slave
Date: 2013-01-17 17:29:52
Message-ID: 50F83510.6050308@vmware.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On 17.01.2013 18:55, Andres Freund wrote:
> On 2013-01-17 18:50:35 +0200, Heikki Linnakangas wrote:
>> I was thinking of the attached. As long as we check for
>> CheckForStandbyTrigger() after the "record == NULL" check, we won't perform
>> extra stat() calls on successful reads, only when we're polling after
>> reaching the end of valid WAL. That seems acceptable.
>
> Looks good to me.

Ok, committed.

- Heikki

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Andres Freund 2013-01-17 17:35:20 Re: Slave enters in recovery and promotes when WAL stream with master is cut + delay master/slave
Previous Message Dimitri Fontaine 2013-01-17 17:06:50 Re: Event Triggers: adding information