| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | oliverrojo(at)anticogroup(dot)com |
| Cc: | Postgresql Mailing List <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: invalid byte sequence for encoding error |
| Date: | 2006-05-19 05:05:19 |
| Message-ID: | 25434.1148015119@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
"Oliver A. Rojo" <oliverrojo(at)anticogroup(dot)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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Oliver A. Rojo | 2006-05-19 05:15:51 | Re: invalid byte sequence for encoding error |
| Previous Message | Oliver A. Rojo | 2006-05-19 04:52:12 | invalid byte sequence for encoding error |