Skip site navigation (1) Skip section navigation (2)

Re: BUG #3700: initdb could not find suitable encoding for locale "Polish_Poland.1250"

From: Dave Page <dpage(at)postgresql(dot)org>
To: Marek Romanowski <marek(dot)romanowski(at)gmail(dot)com>
Cc: pgsql-bugs(at)postgresql(dot)org
Subject: Re: BUG #3700: initdb could not find suitable encoding for locale "Polish_Poland.1250"
Date: 2007-10-26 08:53:06
Message-ID: 4721AAF2.7040005@postgresql.org (view raw or flat)
Thread:
Lists: pgsql-bugs
Marek Romanowski wrote:
> The following bug has been logged online:
> 
> Bug reference:      3700
> Logged by:          Marek Romanowski
> Email address:      marek(dot)romanowski(at)gmail(dot)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.

In response to

pgsql-bugs by date

Next:From: annaiah hDate: 2007-10-26 12:09:55
Subject: connection problem
Previous:From: Magnus HaganderDate: 2007-10-26 08:52:30
Subject: Re: BUG #3700: initdb could not find suitable encoding for locale "Polish_Poland.1250"

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group