Skip site navigation (1) Skip section navigation (2)

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

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Joe <dev(at)freedomcircle(dot)net>
Cc: pgsql-bugs(at)postgresql(dot)org
Subject: Re: Bug #3924: Create Database with another encoding as the encoding from postgres
Date: 2008-10-30 14:39:58
Message-ID: 13392.1225377598@sss.pgh.pa.us (view raw or flat)
Thread:
Lists: pgsql-bugs
Joe <dev(at)freedomcircle(dot)net> writes:
> Going back to my options, are you saying that if I re-initdb the 8.3 
> cluster to UTF8, restore the LATIN1 db as UTF8, and then do "set 
> client_encoding = LATIN1" in the application code, then everything will 
> work fine, even if the machine locale remains en_US.iso88591?

No, you'd have to set the database's locale to en_US.utf8 to do that.

Plan B would be to set the database locale to C, which is
encoding-agnostic and hence allows different databases to have different
encodings.  Do you actually need en_US sort order?

			regards, tom lane

In response to

Responses

pgsql-bugs by date

Next:From: Zdenek KotalaDate: 2008-10-30 14:46:14
Subject: Re: Upgrade from 7.4.5 to 8.3.3
Previous:From: JoeDate: 2008-10-30 14:34:49
Subject: Re: Bug #3924: Create Database with another encoding as the encoding from postgres

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group