Re: BUG #5011: Standby recovery unable to follow timeline change

From: Heikki Linnakangas <heikki(dot)linnakangas(at)enterprisedb(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: James Bardin <jbardin(at)bu(dot)edu>, pgsql-bugs(at)postgresql(dot)org
Subject: Re: BUG #5011: Standby recovery unable to follow timeline change
Date: 2009-08-26 15:35:08
Message-ID: 4A95562C.5090109@enterprisedb.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: 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

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Heikki Linnakangas 2009-08-26 15:36:46 Re: BUG #5011: Standby recovery unable to follow timeline change
Previous Message Jaime Casanova 2009-08-26 15:12:00 Re: BUG #5015: MySQL migration wizard does not start