Re: Possibly corrupted pg_control file after machine crash - Mailing list pgsql-novice

From Greg Stark
Subject Re: Possibly corrupted pg_control file after machine crash
Date
Msg-id 407d949e0907030526x264f07b8td4cd8858c6cd4a49@mail.gmail.com
Whole thread Raw
In response to Possibly corrupted pg_control file after machine crash  (Michael Wood <esiotrot@gmail.com>)
List pgsql-novice
At least the following fields seem to be garbage:

On Fri, Jul 3, 2009 at 12:32 PM, Michael Wood<esiotrot@gmail.com> wrote:
> Maximum data alignment:               0
> Database block size:                  8
> Blocks per segment of large relation: 0
> WAL block size:                       0
> Bytes per WAL segment:                1093850759
> Maximum length of identifiers:        8192
> Maximum columns in an index:          131072
> Maximum size of a TOAST chunk:        8192
> Date/time type storage:               64-bit integers
> Maximum length of locale name:        64
> LC_COLLATE:
> LC_CTYPE:


One option might be to initdb a new database, grab the control file
from there, use pg_resetxlog to restore the important values from your
old control file and then see if you can pick up from there.

--
greg
http://mit.edu/~gsstark/resume.pdf

pgsql-novice by date:

Previous
From: Michael Wood
Date:
Subject: Possibly corrupted pg_control file after machine crash
Next
From: Doug Graham
Date:
Subject: Setting shmmax in /etc/rc on Mac OS X to install Postgres