Re: StartupCLOG - Mailing list pgsql-hackers

From Simon Riggs
Subject Re: StartupCLOG
Date
Msg-id 1220543935.4371.981.camel@ebony.2ndQuadrant
Whole thread Raw
In response to Re: StartupCLOG  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: StartupCLOG  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
On Thu, 2008-09-04 at 11:12 -0400, Tom Lane wrote:
> Simon Riggs <simon@2ndQuadrant.com> writes:
> > I notice that StartupCLOG zeroes out entries later than the nextxid when
> > we complete recovery in StartupXLOG, reason given is safety in case we
> > crash.
> 
> > ISTM that we should also do that whenever we see a Shutdown Checkpoint
> > in WAL, since that can be caused by a shutdown immediate, shutdown abort
> > or crash.
> 
> Er, what?  The definition of a crash is the *lack* of a shutdown
> checkpoint.

Yes, but that's not what I'm saying. 

I was thinking about what happens when you are performing a PITR using
log records that contain a crash/recovery/shutdown checkpoint sequence.

I take it there's no problem there?

-- Simon Riggs           www.2ndQuadrant.comPostgreSQL Training, Services and Support



pgsql-hackers by date:

Previous
From: Andrew Sullivan
Date:
Subject: Re: [PATCH] Cleanup of GUC units code
Next
From: Tom Lane
Date:
Subject: Re: Debugging methods