| From: | Martijn van Oosterhout <kleptog(at)svana(dot)org> |
|---|---|
| To: | "Abraham, Danny" <danny_abraham(at)bmc(dot)com> |
| Cc: | "pgsql-general(at)postgresql(dot)org" <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: initdb fails on Windows with encoding=LATIN1 |
| Date: | 2009-07-19 11:15:07 |
| Message-ID: | 20090719111506.GB18698@svana.org |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On Sun, Jul 19, 2009 at 04:35:43AM -0500, Abraham, Danny wrote:
> We do need LATIN1.
>
> The error message is:
>
> initdb: encoding mismatch
> The encoding you selected (LATIN1) and the encoding that the
> selected locale uses (WIN1252) do not match. This would lead to
> misbehavior in various character string processing functions.
> Rerun initdb and either do not specify an encoding explicitly,
> or choose a matching combination.
Given that WIN1252 is a superset of Latin-1, I'm not sure if this a
real problem. Does windows actually support Latin-1 only without
supporting Win-1251 at the same time?
Have a nice day,
--
Martijn van Oosterhout <kleptog(at)svana(dot)org> http://svana.org/kleptog/
> Please line up in a tree and maintain the heap invariant while
> boarding. Thank you for flying nlogn airlines.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andreas Kretschmer | 2009-07-19 11:48:18 | Re: Timestamp indicies not being used! |
| Previous Message | Martijn van Oosterhout | 2009-07-19 11:08:01 | Re: Best practices for moving UTF8 databases |