Re: Changing Character Sets - Mailing list pgsql-general

From Magnus Hagander
Subject Re: Changing Character Sets
Date
Msg-id CABUevEzutvXw0UR4M5Tt=yCoH30RAABh9btHdad9tWVJjRJ5pA@mail.gmail.com
Whole thread Raw
In response to Re: Changing Character Sets  (Tim Gustafson <tjg@ucsc.edu>)
List pgsql-general
On Tue, Feb 12, 2013 at 6:02 PM, Tim Gustafson <tjg@ucsc.edu> wrote:
>> What you're looking for is to change the encoding, right, and not the locale?
>
> Correct.
>
>> You can't change the encoding of a database, but you can use a
>> different one when you create it - this can be specified in the CREATE
>> DATABASE statement.
>
> That's what I wound up doing.
>
>> You can also ask pg_dump to use a specific encoding using the -E
>> parameter. You can't do it on pg_dumpall, but you can do it if you use
>> pg_dump.
>
> That's good to know.
>
> I'm curious why a pg_dumpall from 8.4 followed by a restore in 9.2
> caused the character sets to change at all.  Was there some change in
> the default character sets between 8.4 and 9.2?

That depends on your platform, but the answer is likely "yes". Or you
had manually specified SQL_ASCII in the 8.4 method. SQL_ASCII
basically means "don't care at all about encodings".


--
 Magnus Hagander
 Me: http://www.hagander.net/
 Work: http://www.redpill-linpro.com/

pgsql-general by date:

Previous
From: Tim Gustafson
Date:
Subject: Re: Changing Character Sets
Next
From: Andrew Taylor
Date:
Subject: ERROR: relative path not allowed for COPY to file