Re: BUG #3924: Create Database with another encoding as the encoding from postgres

Stefan Kunick wrote:
> PostgreSQL version: 8.3RC2
> Operating system:   Windows Longhorn
> Description:        Create Database with another encoding as the encoding
> from postgres
> Details:
>
> I installed postgres with the encoding 1252. After this, i started the
> program createdb (createdb -E LATIN1 -O postgres -p 5555 -U postgres). The
> program stopped with the error message: createdb: database creation failed.
> Error: encoding LATIN1 does not match server's locale German_Germany.1252
> DETAIL: The server's LC_CTYPE setting requires encoding WIN1252.
>
> With the former version 8.2, i can create a database with other encoding

Yes, that's an intentional change. From release notes:

> Disallow database encodings that are inconsistent with the server's locale setting (Tom)
>
> On most platforms, C locale is the only locale that will work with any database encoding. Other locale settings imply
aspecific encoding and will misbehave if the database encoding is something different. (Typical symptoms include bogus
textualsort order and wrong results from upper() or lower().) The server now rejects attempts to create databases that
havean incompatible encoding.  

--
   Heikki Linnakangas
   EnterpriseDB   http://www.enterprisedb.com