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

["Heikki Linnakangas" <heikki(at)enterprisedb(dot)com>]

Pit M. wrote:
> I had the same problem this morning. We provide a sample database with 
> LATIN1 encoding (included in our setup). So how can i change my encoding 
> to have a database that can be used with PG 8.1; 8.1; 8.2 and 8.3 
> without problems and without knowing how the server was installed? What 
> is the required encoding as LATIN1 was the encoding we prefered.  

How exactly are you providing the sample database? If it's in a pg_dump 
format, it should work regardless of the encoding and locale used in initdb.

If you're issuing a CREATE DATABASE command, can't just don't specify 
any encoding and let it use the default?

> We don't want to use UNICODE.

Why not?

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