Re: Encoding woes - Mailing list pgsql-novice

From Tom Lane
Subject Re: Encoding woes
Date
Msg-id 1858.1114526402@sss.pgh.pa.us
Whole thread Raw
In response to Encoding woes  (Bendik R.Johansen <bendik.johansen@gmail.com>)
List pgsql-novice
"Bendik R.Johansen" <bendik.johansen@gmail.com> writes:
> I am having a few encoding related problems.

> 1. I have a database set up on my Mac OSX machine, PostgreSQL 8.02. I
> am trying to dump the tables and load them into Postgres on a Suse 9.2
> box. I get the following error:
> ERROR:  invalid byte sequence for encoding "UNICODE": 0xe5742c

I'm betting that the database encoding on the source machine was set as
SQL_ASCII, but that you then proceeded to store a lot of data that
wasn't plain ASCII.  To load it into a machine with a different database
encoding, you are going to have to be honest about what the data
actually is.  You should modify the dump file to set "client_encoding"
to the correct description of the source data (Latin1 maybe?).  Postgres
can translate Latin1 to Unicode ... but only if it's told what the data
encoding is.

            regards, tom lane

pgsql-novice by date:

Previous
From: Bendik R.Johansen
Date:
Subject: Encoding woes
Next
From: "Keith Worthington"
Date:
Subject: Re: audit information