| From: | Curt Sampson <cjs(at)cynic(dot)net> |
|---|---|
| To: | Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> |
| Cc: | pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: WAL replay logic (was Re: [PERFORM] Mount options for |
| Date: | 2003-02-18 05:26:46 |
| Message-ID: | Pine.NEB.4.51.0302181426040.386@angelic-vtfw.cvpn.cynic.net |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers pgsql-performance |
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(at)cynic(dot)net> +81 90 7737 2974 http://www.netbsd.org
Don't you know, in this new Dark Age, we're all light. --XTC
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Curt Sampson | 2003-02-18 05:37:37 | Re: Detecting corrupted pages earlier |
| Previous Message | Bruce Momjian | 2003-02-18 05:18:00 | Re: Non-colliding auto generated names |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Chantal Ackermann | 2003-02-18 10:28:40 | Re: cost and actual time |
| Previous Message | Bruce Momjian | 2003-02-18 05:15:43 | Re: [HACKERS] WAL replay logic (was Re: Mount options for |