Re: BUG #14197: ERROR: character with byte sequence 0x81 in encoding "WIN1252" has no equivalent in encoding "UTF8" - Mailing list pgsql-bugs

From John R Pierce
Subject Re: BUG #14197: ERROR: character with byte sequence 0x81 in encoding "WIN1252" has no equivalent in encoding "UTF8"
Date
Msg-id 04ed1adc-e84b-e048-27af-c8e84844e9b7@hogranch.com
Whole thread Raw
In response to Re: BUG #14197: ERROR: character with byte sequence 0x81 in encoding "WIN1252" has no equivalent in encoding "UTF8"  (<sheri.bhavani@cognizant.com>)
Responses Re: BUG #14197: ERROR: character with byte sequence 0x81 in encoding "WIN1252" has no equivalent in encoding "UTF8"  ("Albin, Lloyd P" <lalbin@scharp.org>)
List pgsql-bugs
On 6/16/2016 10:08 PM, sheri.bhavani@cognizant.com wrote:
> ·ERROR: character with byte sequence 0x81 in encoding "WIN1252" has no
> equivalent in encoding "UTF8" is thrown in postgreSQL 9.5.3 .

per https://en.wikipedia.org/wiki/Windows-1252  0x81 is not a valid
character in encoding win1252, so it can't be converted to UTF8

you need to determine what field of which row of what table has that
value in it and change it to something valid (perhaps 0x20 ?) before you
can load this data into a UTF8 database.



--
john r pierce, recycling bits in santa cruz

pgsql-bugs by date:

Previous
From:
Date:
Subject: Re: BUG #14197: ERROR: character with byte sequence 0x81 in encoding "WIN1252" has no equivalent in encoding "UTF8"
Next
From: Torsten Zuehlsdorff
Date:
Subject: Re: BUG #14198: IPv6 address validation broken