Re: Hard drive failure leads to corrupt db

From: "Brusser, Michael" <Michael(dot)Brusser(at)matrixone(dot)com>
To: "Pgsql-Hackers" <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Hard drive failure leads to corrupt db
Date: 2005-09-13 12:49:23
Message-ID: DAF7A2046DD4A24F8F77B086F840BF190125142B@msx11am.matrixone.net
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Just occurred to me: perhaps we don't have a database corruption,
instead after replacement of the boot drive the locale on the host
changed from
en_US.ISO8859-1 to 'C'

Still I am not sure what to do. Is changing the locale back to
en_US.ISO8859-1
the right thing to do now?

Mike.

-----Original Message-----

Our customer reported a problem resulting from the hard drive failure.
Database server would not start, generating this message:
PANIC: The database cluster was initialized with LC_COLLATE
'en_US.ISO8859-1',
which is not recognized by setlocale().
It looks like you need to initdb.

They are running v.7.3.2 on Solaris, where all locale parameters are set
to "C".
Is there anything we can do to restore the database without data loss?

Thank you,
Michael.

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Michael Paesold 2005-09-13 13:41:22 Bug with cursor declaration in PL/pgSQL in CVS tip?
Previous Message Brusser, Michael 2005-09-13 12:34:49 Hard drive failure leads to corrupt db