From: | "Scott Marlowe" <scott(dot)marlowe(at)gmail(dot)com> |
---|---|
To: | "Claus Guttesen" <kometen(at)gmail(dot)com> |
Cc: | pgsql-admin(at)postgresql(dot)org |
Subject: | Re: iso-8859-1 and utf-8 |
Date: | 2008-09-25 08:13:00 |
Message-ID: | dcc563d10809250113y363beff6p1527ce4d851eb9d7@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-admin |
On Thu, Sep 25, 2008 at 1:59 AM, Claus Guttesen <kometen(at)gmail(dot)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
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2008-09-25 13:24:08 | Re: missing chunk number 0 for toast value |
Previous Message | Claus Guttesen | 2008-09-25 07:59:31 | iso-8859-1 and utf-8 |