Re: ERROR: character 0x90 of encoding "WIN1252" has no equivalent in "UTF8"

From: "Wang, Mary Y" <mary(dot)y(dot)wang(at)boeing(dot)com>
To: Alban Hertroys <dalroi(at)solfertje(dot)student(dot)utwente(dot)nl>
Cc: "pgsql-general(at)postgresql(dot)org" <pgsql-general(at)postgresql(dot)org>
Subject: Re: ERROR: character 0x90 of encoding "WIN1252" has no equivalent in "UTF8"
Date: 2010-06-05 14:07:35
Message-ID: FA20D4C4FEBFD148B1C0CB09913825FC04589DD9A9@XCH-SW-06V.sw.nos.boeing.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

Thanks Alban, but I'm still confused.
I just read the PostgreSQL manual, and got the impression that UTF8 would take care of ALL character sets, so I put SET client_encoding = 'UTF8' in the dump file, and reload it again, then I got even more errors like:
psql:/tmp/060410finalsr15dump.txt:31430: ERROR: invalid byte sequence for encoding "UTF8": 0x93
psql:/tmp/060410finalsr15dump.txt:31795: ERROR: invalid byte sequence for encoding "UTF8": 0x93
psql:/tmp/060410finalsr15dump.txt:31826: ERROR: invalid byte sequence for encoding "UTF8": 0x85
psql:/tmp/060410finalsr15dump.txt:31827: ERROR: invalid byte sequence for encoding "UTF8": 0x92
psql:/tmp/060410finalsr15dump.txt:31874: ERROR: invalid byte sequence for encoding "UTF8": 0x93
psql:/tmp/060410finalsr15dump.txt:32111: ERROR: invalid byte sequence for encoding "UTF8": 0x93
psql:/tmp/060410finalsr15dump.txt:32112: ERROR: invalid byte sequence for encoding "UTF8": 0x92

What is the client encoding that I should set to so that it would take care all character sets? http://www.postgresql.org/docs/8.3/interactive/multibyte.html

Any suggestions?
Thanks
Mary

-----Original Message-----
From: Alban Hertroys [mailto:dalroi(at)solfertje(dot)student(dot)utwente(dot)nl]
Sent: Saturday, June 05, 2010 1:35 AM
To: Wang, Mary Y
Cc: pgsql-general(at)postgresql(dot)org
Subject: Re: [GENERAL] ERROR: character 0x90 of encoding "WIN1252" has no equivalent in "UTF8"

On 5 Jun 2010, at 4:44, Wang, Mary Y wrote:

> Hi,
>
> I'm getting this error from postgres " ERROR: character 0x90 of encoding "WIN1252" has no equivalent in "UTF8" " and from a dump file when I tried to use psql command to restore the dump.
>
> I have SET client_encoding = 'win1252' in the dump file.
>
> Any ideas?

Apparently Win1252 is the not the right encoding to use for your data, as 0x90 is undefined in that encoding. See http://dbaspot.com/forums/ingres-database/414795-re-info-ingres-fw-how-insert-control-charactersintovarcharcolumn.html for someone with the same problem (on Ingres) and links to two different code pages listing the characters therein.

Alban Hertroys

--
If you can't see the forest for the trees, cut the trees and you'll see there is no forest.

!DSPAM:1099,4c0a0c3410156830940052!

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Tom Lane 2010-06-05 15:06:16 Re: so, does this overlap or not...? - fencepost question on overlaps()
Previous Message Tom Lane 2010-06-05 13:41:14 Re: Null comparisons and the transform_null_equals run-time parameter