Re: Clean shutdown and warm standby - Mailing list pgsql-hackers

From Guillaume Smet
Subject Re: Clean shutdown and warm standby
Date
Msg-id 1d4e0c10905271435u339c2afal4fb23a75570f534d@mail.gmail.com
Whole thread Raw
In response to Re: Clean shutdown and warm standby  (Guillaume Smet <guillaume.smet@gmail.com>)
Responses Re: Clean shutdown and warm standby  (Heikki Linnakangas <heikki.linnakangas@enterprisedb.com>)
List pgsql-hackers
On Tue, Apr 28, 2009 at 5:35 PM, Guillaume Smet
<guillaume.smet@gmail.com> wrote:
> On Tue, Apr 28, 2009 at 5:22 PM, Heikki Linnakangas
> <heikki.linnakangas@enterprisedb.com> wrote:
>> At a normal startup, the checkpoint record would be there as usual. And an
>> archive recovery starts at the location indicated by the backup label.
>>
>> AFAICS calling RequestXLogSwitch() before CreateCheckPoint would be
>> equivalent to calling "pg_switch_xlog()" just before shutting down.
>
> That's what I had in mind when writing the patch but I didn't know the
> implications of this particular checkpoint.
>
> So moving the call before CreateCheckPoint is what I really intended
> now that I have in mind these implications and I don't know why it would be
> a problem to miss this checkpoint in the logs archived.

What do we decide about this problem?

Should we just call RequestXLogSwitch() before the creation of the
shutdown checkpoint or do we need a more complex patch? If so can
anybody explain the potential problem of this approach so we can
figure how to fix it?

Thanks.

-- 
Guillaume


pgsql-hackers by date:

Previous
From: Caleb Welton
Date:
Subject: Re: [PATCH] plpythonu datatype conversion improvements
Next
From: "Larry Silvermintz"
Date:
Subject: Need 8.4 chm.