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

From: John R Pierce <pierce(at)hogranch(dot)com>
To: sheri(dot)bhavani(at)cognizant(dot)com, pgsql-bugs(at)postgresql(dot)org
Subject: Re: BUG #14197: ERROR: character with byte sequence 0x81 in encoding "WIN1252" has no equivalent in encoding "UTF8"
Date: 2016-06-17 08:04:26
Message-ID: 04ed1adc-e84b-e048-27af-c8e84844e9b7@hogranch.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

On 6/16/2016 10:08 PM, sheri(dot)bhavani(at)cognizant(dot)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

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Torsten Zuehlsdorff 2016-06-17 13:18:48 Re: BUG #14198: IPv6 address validation broken
Previous Message Michael Paquier 2016-06-17 06:35:25 Re: pg_dump doesn't dump new objects created in schemas from extensions