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

From: Peter Eisentraut <peter_e(at)gmx(dot)net>
To: pgsql-bugs(at)postgresql(dot)org
Cc: "Stefan Kunick" <stefan(at)kunick(dot)org>
Subject: Re: BUG #3924: Create Database with another encoding as the encoding from postgres
Date: 2008-02-02 19:45:12
Message-ID: 200802022045.13439.peter_e@gmx.net
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

Stefan Kunick wrote:
> 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

You could, but the result wouldn't have worked correctly. You need to pick
locales and encodings that match. This was always true, but not it is
enforced.

--
Peter Eisentraut
http://developer.postgresql.org/~petere/

In response to

Browse pgsql-bugs by date

  From Date Subject
Next Message Heikki Linnakangas 2008-02-02 20:35:12 Re: BUG #3924: Create Database with another encoding as the encoding from postgres
Previous Message Stefan Kunick 2008-02-02 19:20:48 BUG #3925: You can delete enum elements from pg_enum, but it is used in a table