[HACKERS] Hard drive failure leads to corrupt db

2005-09-13 Thread Brusser, Michael
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

Re: [HACKERS] Hard drive failure leads to corrupt db

2005-09-13 Thread Brusser, Michael
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

Re: [HACKERS] Hard drive failure leads to corrupt db

2005-09-13 Thread Peter Eisentraut
Brusser, Michael wrote: 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(). The issue is

Re: [HACKERS] Hard drive failure leads to corrupt db

2005-09-13 Thread Martijn van Oosterhout
Your problem is that your database was initialised with locale 'en_US.ISO8859-1' but your system no longer recognises it. You need to create the locale somehow. On Linux it's /etc/locale.gen but you should probably search the locale manpage for how to do it on Solaris. Changing the locale

Re: [HACKERS] Hard drive failure leads to corrupt db

2005-09-13 Thread Tom Lane
Peter Eisentraut [EMAIL PROTECTED] writes: Brusser, Michael wrote: 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