From: Peter Eisentraut <peter_e@gmx.net>
To: Frank Finner <postgresql@finner.de>
Cc: pgsql-admin@postgresql.org
Cc: lloyd@middleware-company.com
Cc: eric@middleware-company.com
Subject: Re: Going from a DB using SQL_ASCII to UNICODE
Date: Wed, 21 Apr 2004 11:51:30 +0200
Message-ID: <200404211151.30593.peter_e@gmx.net> (raw)
In-Reply-To: <20040420070551.385713b2.postgresql@finner.de>
References: <E1BFegz-00035r-2w@server1070.gisol.com>
<20040420070551.385713b2.postgresql@finner.de>
Am Dienstag, 20. April 2004 07:05 schrieb Frank Finner:
> I answered to a similiar problem on the [GENERAL] list a few days ago. In
> short: You can use "recode" in a pipe between dump and restore like
> "pg_dump database|recode ascii..utf8|psql newdatabase" to get rid of
> unicode problems while transferring from a different encoding. Please look
> at my statements on the[GENERAL] list for the gory details.
This is not necessary. You just need to set the client encoding correctly
(not SQL_ASCII, but something like LATIN1). The encoding conversion happens
automatically, as usual.
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients from your mail client; the link fills in
the headers below: reply via email
Some clients, webmail especially, drop In-Reply-To and References from
a link, and the reply then starts a new thread: use the mbox below.
To: pgsql-admin@postgresql.org
Cc: peter_e@gmx.net, postgresql@finner.de, lloyd@middleware-company.com, eric@middleware-company.com
Subject: Re: Going from a DB using SQL_ASCII to UNICODE
In-Reply-To: <200404211151.30593.peter_e@gmx.net>
References: <E1BFegz-00035r-2w@server1070.gisol.com> <20040420070551.385713b2.postgresql@finner.de> <200404211151.30593.peter_e@gmx.net>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox