| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Peter Eisentraut <peter_e(at)gmx(dot)net> |
| Cc: | pgsql-hackers(at)postgresql(dot)org, "Brusser, Michael" <Michael(dot)Brusser(at)matrixone(dot)com> |
| Subject: | Re: Hard drive failure leads to corrupt db |
| Date: | 2005-09-13 15:27:31 |
| Message-ID: | 23454.1126625251@sss.pgh.pa.us |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Peter Eisentraut <peter_e(at)gmx(dot)net> 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 recognized by setlocale().
> The issue is that the operating system does not recognize that locale
> name. Perhaps you need to install some extra packages to get the full
> locale support.
Yes. The database definitely was in en_US.ISO8859-1 locale, even if you
thought otherwise. That information comes from inside the pg_control
file, which is CRC-checked, so it's highly unlikely that corruption of
pg_control would have resulted in this message. I think it's much more
likely that you lost the files that setlocale needs to define this
locale.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Greg Stark | 2005-09-13 15:37:24 | Re: Spinlocks, yet again: analysis and proposed patches |
| Previous Message | Roman Neuhauser | 2005-09-13 14:47:14 | bug #1702: nested composite types in plpgsql |