From: Scott Marlowe <scott.marlowe@gmail.com>
To: Claus Guttesen <kometen@gmail.com>
Cc: pgsql-admin@postgresql.org
Subject: Re: iso-8859-1 and utf-8
Date: Thu, 25 Sep 2008 02:13:00 -0600
Message-ID: <dcc563d10809250113y363beff6p1527ce4d851eb9d7@mail.gmail.com> (raw)
In-Reply-To: <b41c75520809250059n9a657abj3397b3e163b996bd@mail.gmail.com>
References: <b41c75520809250059n9a657abj3397b3e163b996bd@mail.gmail.com>
On Thu, Sep 25, 2008 at 1:59 AM, Claus Guttesen <kometen@gmail.com> wrote:
> Hi.
>
> I found out by accident that my db-dump, at least in ver. 8.3.3,
> automagically converts from iso-8859-1 to utf-8. Our db has been
> around since January 2000 and iso-8859-1 was chosen back then as
> encoding. When I occasionally imported the nightly dump to a test-db
> it would complain very early during the import and abort if the
> encoding was incorrect. I think this was also the case with 8.3.1
> although I'm not certain.
I'm guessing that the client encoding is set to utf-8 instead of
iso-8859-1 on the client end. pg automatically converts to the client
encoding of the user connecting / environment.
I know that at least 8.2 supports the -E switch to set client encoding.
psql --help
MUCH SNIPPED:
-E, --encoding=ENCODING dump the data in encoding ENCODING
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 using the --to and --cc options:
reply via email
To: pgsql-admin@postgresql.org
Cc: scott.marlowe@gmail.com, kometen@gmail.com
Subject: Re: iso-8859-1 and utf-8
In-Reply-To: <dcc563d10809250113y363beff6p1527ce4d851eb9d7@mail.gmail.com>
* 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