Re: v7.4 pg_dump(all) need to encode from SQL_ASCII to UTF8 - Mailing list pgsql-general

From Dean Gibson (DB Administrator)
Subject Re: v7.4 pg_dump(all) need to encode from SQL_ASCII to UTF8
Date
Msg-id 47C1F2C2.5060702@ultimeth.com
Whole thread Raw
In response to v7.4 pg_dump(all) need to encode from SQL_ASCII to UTF8  (Ralph Smith <smithrn@washington.edu>)
List pgsql-general
On 2008-02-22 17:57, Ralph Smith wrote:
> I'm looking at the v7.4 manuals and I don't see how to encode for
> importing into a v8 DB using UTF8.
>
> Maybe I'm making this hard on myself?
> The old DB is using SQL_ASCII.
> We'd like the new one to use UTF8.
>
> As development proceeds, I'm going to have to do this regularly, both
> the entire DB and by tables.
> If not for the encoding, I've got all that down, even automated.
>
> Thanks for any help!
> Ralph
>
> -------------------------------
> p.s.  Isn't there a 16 bit Unicode for postgreSQL?
>
> smithrn at u dot washington dot edu
>

There's nothing to do.  Dump the database in ASCII; create the new
database with a server_encoding of UTF-8; and import the data (which is
marked as having a client_encoding of SQL_ASCII).

ps: No.

--
Mail to my list address MUST be sent via the mailing list.
All other mail to my list address will bounce.


pgsql-general by date:

Previous
From: Tom Lane
Date:
Subject: Re: plpgsql function
Next
From: James Robinson
Date:
Subject: no-arg cluster and locks ...