DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma;
	h=message-id:date:from:to:subject:cc:in-reply-to:mime-version
	:content-type:content-transfer-encoding:content-disposition
	:references;
	b=hSTrl2fi2DZrpWYmnvHgjWOGp59sLnz3C+7EaViqNO9AanYq+emTioSXl6AH3ujBSx
	hSJrcwo26+5DSgOGlD9xDyQOdDdRLwATbp00Gk/EDJJpdiFuU3dWDHyuntt2nlBK/Oby
	TCrRZtsLAx8yrQMJgVc+iAKKJotTre4Y3eQA0=
Message-ID: <dcc563d10809250113y363beff6p1527ce4d851eb9d7@mail.gmail.com>
Date: Thu, 25 Sep 2008 02:13:00 -0600
From: "Scott Marlowe" <scott.marlowe@gmail.com>
To: "Claus Guttesen" <kometen@gmail.com>
Subject: Re: iso-8859-1 and utf-8
Cc: pgsql-admin@postgresql.org
In-Reply-To: <b41c75520809250059n9a657abj3397b3e163b996bd@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
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