Re: BUG #3700: initdb could not find suitable encoding for locale "Polish_Poland.1250" - Mailing list pgsql-bugs

From Dave Page
Subject Re: BUG #3700: initdb could not find suitable encoding for locale "Polish_Poland.1250"
Date
Msg-id 4721AAF2.7040005@postgresql.org
Whole thread Raw
In response to BUG #3700: initdb could not find suitable encoding for locale "Polish_Poland.1250"  ("Marek Romanowski" <marek.romanowski@gmail.com>)
List pgsql-bugs
Marek Romanowski wrote:
> The following bug has been logged online:
>
> Bug reference:      3700
> Logged by:          Marek Romanowski
> Email address:      marek.romanowski@gmail.com
> PostgreSQL version: 8.3-beta1
> Operating system:   Windows XP Professional
> Description:        initdb could not find suitable encoding for locale
> "Polish_Poland.1250"
> Details:
>
> I've installed 8.2 yesterday and everything was ok,
> so I think it's some kind of regression bug.
>
> Second run was with -E LATIN2 option, so encoding was
> given clearly, database was initialized, but some
> warnings about encoding showed up too.
>
>
>
> $ ./initdb -D "c:\java\pgdata-8.3"
> The files belonging to this database system will be owned by user
> "efigence".
> This user must also own the server process.
>
> The database cluster will be initialized with locale Polish_Poland.1250.
> could not determine encoding for locale "Polish_Poland.1250": codeset is
> "CP1250"
> initdb: could not find suitable encoding for locale "Polish_Poland.1250"
> Rerun initdb with the -E option.

This should be OK in beta2. WIN1250 accidentally got left out of a table
in beta 1.

Regards, Dave.

pgsql-bugs by date:

Previous
From: Magnus Hagander
Date:
Subject: Re: BUG #3700: initdb could not find suitable encoding for locale "Polish_Poland.1250"
Next
From: "annaiah h"
Date:
Subject: connection problem