Re: Possibly corrupted pg_control file after machine crash

From: Greg Stark <gsstark(at)mit(dot)edu>
To: Michael Wood <esiotrot(at)gmail(dot)com>
Cc: pgsql-novice(at)postgresql(dot)org
Subject: Re: Possibly corrupted pg_control file after machine crash
Date: 2009-07-03 12:26:55
Message-ID: 407d949e0907030526x264f07b8td4cd8858c6cd4a49@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-novice

At least the following fields seem to be garbage:

On Fri, Jul 3, 2009 at 12:32 PM, Michael Wood<esiotrot(at)gmail(dot)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

In response to

Browse pgsql-novice by date

  From Date Subject
Next Message Doug Graham 2009-07-03 13:47:21 Setting shmmax in /etc/rc on Mac OS X to install Postgres
Previous Message Michael Wood 2009-07-03 11:32:57 Possibly corrupted pg_control file after machine crash