Re: Re: BUG #3924: Create Database with another encoding as the encoding from postgres - Mailing list pgsql-bugs

From Heikki Linnakangas
Subject Re: Re: BUG #3924: Create Database with another encoding as the encoding from postgres
Date
Msg-id 47AC61BB.3010608@enterprisedb.com
Whole thread Raw
In response to Re: BUG #3924: Create Database with another encoding as the encoding from postgres  ("Pit M." <fmi-soft@gmx.de>)
List pgsql-bugs
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

pgsql-bugs by date:

Previous
From: Gary Doades
Date:
Subject: Re: BUG #3941: Insert Error
Next
From: "Valentine Gogichashvili"
Date:
Subject: BUG #3942: Related to BUG #2568 and BUG #2859: VACUUM process hangs and does not respond to the kill signals