Re: WAL replay logic (was Re: [PERFORM] Mount options for - Mailing list pgsql-hackers

From Bruce Momjian
Subject Re: WAL replay logic (was Re: [PERFORM] Mount options for
Date
Msg-id 200302181908.h1IJ8Ge19074@candle.pha.pa.us
Whole thread Raw
In response to Re: WAL replay logic (was Re: [PERFORM] Mount options for  (Curt Sampson <cjs@cynic.net>)
List pgsql-hackers
Uh, not sure.  Does it guard against corrupt WAL records?

---------------------------------------------------------------------------

Curt Sampson wrote:
> On Tue, 18 Feb 2003, Bruce Momjian wrote:
> 
> >
> > Added to TODO:
> >
> >     * Allow WAL information to recover corrupted pg_controldata
> >...
> > >      Using pg_control to get the checkpoint position speeds up the
> > >      recovery process, but to handle possible corruption of pg_control,
> > >      we should actually implement the reading of existing log segments
> > >      in reverse order -- newest to oldest -- in order to find the last
> > >      checkpoint. This has not been implemented, yet.
> 
> So if you do this, do you still need to store that information in
> pg_control at all?
> 
> cjs
> -- 
> Curt Sampson  <cjs@cynic.net>   +81 90 7737 2974   http://www.netbsd.org
>     Don't you know, in this new Dark Age, we're all light.  --XTC
> 
> ---------------------------(end of broadcast)---------------------------
> TIP 5: Have you checked our extensive FAQ?
> 
> http://www.postgresql.org/users-lounge/docs/faq.html
> 

--  Bruce Momjian                        |  http://candle.pha.pa.us pgman@candle.pha.pa.us               |  (610)
359-1001+  If your life is a hard drive,     |  13 Roberts Road +  Christ can be your backup.        |  Newtown Square,
Pennsylvania19073
 


pgsql-hackers by date:

Previous
From: "Ron Mayer"
Date:
Subject: Re: Hard problem with concurrency
Next
From: "Mikheev, Vadim"
Date:
Subject: Re: WAL replay logic (was Re: [PERFORM] Mount options f