Re: Time-Delayed Standbys - Mailing list pgsql-hackers

From Fabrízio de Royes Mello
Subject Re: Time-Delayed Standbys
Date
Msg-id CAFcNs+qD0AJ=qzhsHD9+v_Mhz0RTBJ=cJPCT_T=uT_JvvnC1FQ@mail.gmail.com
Whole thread Raw
In response to Re: Time-Delayed Standbys  (Fabrízio de Royes Mello <fabriziomello@gmail.com>)
Responses Re: Time-Delayed Standbys
List pgsql-hackers

On Thu, Dec 12, 2013 at 3:42 PM, Fabrízio de Royes Mello <fabriziomello@gmail.com> wrote:
>
> On Thu, Dec 12, 2013 at 3:39 PM, Simon Riggs <simon@2ndquadrant.com> wrote:
> >
> > On 12 December 2013 15:19, Simon Riggs <simon@2ndquadrant.com> wrote:
> >
> > > Don't panic guys! I meant UTC offset only. And yes, it may not be
> > > needed, will check.
> >
> > Checked, all non-UTC TZ offsets work without further effort here.
> >
>
> Thanks!
>

Reviewing the committed patch I noted that the "CheckForStandbyTrigger()" after the delay was removed.

If we promote the standby during the delay and don't check the trigger immediately after the delay, then we will replay undesired WALs records.

The attached patch add this check.

Regards,

--
Fabrízio de Royes Mello
Consultoria/Coaching PostgreSQL
>> Timbira: http://www.timbira.com.br
>> Blog sobre TI: http://fabriziomello.blogspot.com
>> Perfil Linkedin: http://br.linkedin.com/in/fabriziomello
>> Twitter: http://twitter.com/fabriziomello
Attachment

pgsql-hackers by date:

Previous
From: Christophe Pettus
Date:
Subject: "stuck spinlock"
Next
From: Florian Pflug
Date:
Subject: Re: ANALYZE sampling is too good