Re: Hard drive failure leads to corrupt db - Mailing list pgsql-hackers

From Brusser, Michael
Subject Re: Hard drive failure leads to corrupt db
Date
Msg-id DAF7A2046DD4A24F8F77B086F840BF190125142B@msx11am.matrixone.net
Whole thread Raw
In response to Hard drive failure leads to corrupt db  ("Brusser, Michael" <Michael.Brusser@matrixone.com>)
Responses Re: Hard drive failure leads to corrupt db
List 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.



pgsql-hackers by date:

Previous
From: "Brusser, Michael"
Date:
Subject: Hard drive failure leads to corrupt db
Next
From: Greg Stark
Date:
Subject: Re: Spinlocks, yet again: analysis and proposed patches