[prev in list] [next in list] [prev in thread] [next in thread] 

List:       pgsql-bugs
Subject:    Re: [BUGS] BUG #3700: initdb could not find suitable encoding for
From:       Dave Page <dpage () postgresql ! org>
Date:       2007-10-26 8:53:06
Message-ID: 4721AAF2.7040005 () postgresql ! org
[Download RAW message or body]

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.

---------------------------(end of broadcast)---------------------------
TIP 5: don't forget to increase your free space map settings
[prev in list] [next in list] [prev in thread] [next in thread]