Re: production server down - Mailing list pgsql-hackers

From Tom Lane
Subject Re: production server down
Date
Msg-id 2608.1103130354@sss.pgh.pa.us
Whole thread Raw
In response to Re: production server down  (Joe Conway <mail@joeconway.com>)
Responses Re: production server down
List pgsql-hackers
Joe Conway <mail@joeconway.com> writes:
> 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?

pg_resetxlog will rebuild it in any case.  However it will re-use the
existing contents as much as it can (if you don't use any of the command
line options to override values).  Given Alvaro's observation that the
existing file looks suspiciously close to a freshly-initdb'd one, I
don't think you want to trust the existing contents.

> 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?

What if anything have you got in $PGDATA/pg_xlog?
        regards, tom lane


pgsql-hackers by date:

Previous
From: Jan Wieck
Date:
Subject: Re: bgwriter changes
Next
From: Dave Cramer
Date:
Subject: Re: [INTERFACES] postgresql-7.4.5