Thread: initdb --locale=LATIN1 fails on Windows

The same command worked fine on PG 8.2.4.

Now, using 8.3.7, the command succeeds only with locale 1252.
It comments something on wrong lc_ctype.

Any idea?

Thanks

Danny

"Abraham, Danny" <danny_abraham@bmc.com> writes:

Yeah, it should fail.  LATIN1 is not a locale name.

> The same command worked fine on PG 8.2.4.

If so, that was a bug in 8.2.

            regards, tom lane

Do you by chance know what is the ISO88591 locale to be used on Windows?

It should be something like Americam_United States.ISO88591.

Thanks

Danny

Actually the command is:    initdb --encoding=LATIN1.

It fails on Windos. fails on Windows

The same command worked fine on PG 8.2.4.

Now, using 8.3.7, the command succeeds only with encoding 1252.
It comments something on wrong lc_ctype.

Thanks

Danny

On Wednesday 15 July 2009 23:02:47 Abraham, Danny wrote:
> Actually the command is:    initdb --encoding=LATIN1.
>
> It fails on Windos. fails on Windows
>
> The same command worked fine on PG 8.2.4.
>
> Now, using 8.3.7, the command succeeds only with encoding 1252.
> It comments something on wrong lc_ctype.

You need to also set the right locale to match the encoding you chose.