Re: BUG #5011: Standby recovery unable to follow timeline change - Mailing list pgsql-bugs

From Heikki Linnakangas
Subject Re: BUG #5011: Standby recovery unable to follow timeline change
Date
Msg-id 4A95562C.5090109@enterprisedb.com
Whole thread Raw
In response to Re: BUG #5011: Standby recovery unable to follow timeline change  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: BUG #5011: Standby recovery unable to follow timeline change  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-bugs
Tom Lane wrote:
> I wrote:
>> ... but this solution is astonishingly ugly.  I think we should move up
>> the LocalSetXLogInsertAllowed call, instead.
>
> Specifically, I propose this patch instead.

It looks better, but leaves the door open for WAL insertions for a much
longer period. Particularly, there's the call to CheckpointGuts(), which
does a lot of things. Maybe I'm just too paranoid about keeping that
sanity check as tight as possible...

> I'm not set up to try the test case though, can you do that?

Sure.

--
  Heikki Linnakangas
  EnterpriseDB   http://www.enterprisedb.com

pgsql-bugs by date:

Previous
From: Jaime Casanova
Date:
Subject: Re: BUG #5015: MySQL migration wizard does not start
Next
From: Heikki Linnakangas
Date:
Subject: Re: BUG #5011: Standby recovery unable to follow timeline change