Re: ERROR: character 0x90 of encoding "WIN1252" has no equivalent in "UTF8" - Mailing list pgsql-general

From Alban Hertroys
Subject Re: ERROR: character 0x90 of encoding "WIN1252" has no equivalent in "UTF8"
Date
Msg-id 16D29B07-312B-484E-BFE4-6C10AAB72AC8@solfertje.student.utwente.nl
Whole thread Raw
In response to ERROR: character 0x90 of encoding "WIN1252" has no equivalent in "UTF8"  ("Wang, Mary Y" <mary.y.wang@boeing.com>)
Responses Re: ERROR: character 0x90 of encoding "WIN1252" has no equivalent in "UTF8"  ("Wang, Mary Y" <mary.y.wang@boeing.com>)
List pgsql-general
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"  "
andfrom 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
forsomeone 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:737,4c0a0c3a10151431365867!



pgsql-general by date:

Previous
From: Konstantin Izmailov
Date:
Subject: Re: parsing geometric operators
Next
From: Manohar Bhattarai
Date:
Subject: Re: [ADMIN] Exception while accessing database