| From: | Joe Conway <mail(at)joeconway(dot)com> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | "Hackers (PostgreSQL)" <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: production server down |
| Date: | 2004-12-15 16:56:19 |
| Message-ID: | 41C06CB3.6010107@joeconway.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Tom Lane wrote:
> My advice is to backup the $PGDATA tree (which you said was in
> progress), then pg_resetxlog, then cross-check the hell out of the data
> you see. Only if you can detect some data problems can we guess at
> something else to do ...
>
Before running pg_resetxlog, a couple of questions:
1. Since it appears that pg_control is suspect, should I force it to be
rebuilt, and if so, how?
2. At the end of GuessControlValues is this comment:
/*
* XXX eventually, should try to grovel through old XLOG to develop
* more accurate values for startupid, nextXID, and nextOID.
*/
What would be involved in doing this, and do you think it would be
worth it?
Thanks,
Joe
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Jan Wieck | 2004-12-15 16:59:09 | Re: bgwriter changes |
| Previous Message | Jan Wieck | 2004-12-15 16:16:26 | Re: [Testperf-general] BufferSync and bgwriter |