Re: invalid byte sequence for encoding error - Mailing list pgsql-general

From Tom Lane
Subject Re: invalid byte sequence for encoding error
Date
Msg-id 25434.1148015119@sss.pgh.pa.us
Whole thread Raw
In response to invalid byte sequence for encoding error  ("Oliver A. Rojo" <oliverrojo@anticogroup.com>)
Responses Re: invalid byte sequence for encoding error  ("Oliver A. Rojo" <oliverrojo@anticogroup.com>)
List pgsql-general
"Oliver A. Rojo" <oliverrojo@anticogroup.com> writes:
> I've just recently upgraded my database from 7.4.8 to 8.0.1. Im dumping
> data i got from my old db to my new db but eventually an error occured

> ERROR:  invalid byte sequence for encoding "UNICODE": 0xd141

That's definitely not valid UNICODE (UTF-8) data.  You need to fix up
your data.  My guess is that what you have stored isn't really UTF-8
but something else (maybe one of the LATINn family).  If so, adjusting
the "SET client_encoding" line in the dump file and trying again should
help.

PG is certainly moving in the direction of more rather than less
encoding checking, so this is something you gotta deal with.

            regards, tom lane

pgsql-general by date:

Previous
From: "Oliver A. Rojo"
Date:
Subject: invalid byte sequence for encoding error
Next
From: "Oliver A. Rojo"
Date:
Subject: Re: invalid byte sequence for encoding error