Postgres Pro
Downloads
Home   >   mailing lists

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

From David G. Johnston
Subject Re: BUG #14197: ERROR: character with byte sequence 0x81 in encoding "WIN1252" has no equivalent in encoding "UTF8"
Date
Msg-id CAKFQuwa8hqnJ0hHDmBN7io15ho3JWJ4F7_trUZ4nOcLCj_1sqg@mail.gmail.com
Whole thread Raw
In response to BUG #14197: ERROR: character with byte sequence 0x81 in encoding "WIN1252" has no equivalent in encoding "UTF8"  (sheri.bhavani@cognizant.com)
List pgsql-bugs
Tree view 
On Thu, Jun 16, 2016 at 8:22 AM, <sheri.bhavani@cognizant.com> wrote:

> The following bug has been logged on the website:
>
> Bug reference:      14197
> Logged by:          bhavani sheri
> Email address:      sheri.bhavani@cognizant.com
> PostgreSQL version: 9.5.3
> Operating system:   Windows7
> Description:
>
> I have migrated from postgreSQL 7 to postgreSQL 9.5.3 and thus getting th=
is
> error.Please help me to resolve it.
>

I'd start with:

Google:  =E2=80=8B
 fixing character with byte sequence postgresql

=E2=80=8BYou use the past tense here "I have migrated" - did the migration =
succeed
and you are getting errors during normal operations or has some aspect of
your migration failed?

David J.=E2=80=8B

pgsql-bugs by date:

Previous
From: sheri.bhavani@cognizant.com
Date:
Subject: BUG #14197: ERROR: character with byte sequence 0x81 in encoding "WIN1252" has no equivalent in encoding "UTF8"
Next
From: yobas@bk.ru
Date:
Subject: BUG #14194: Why do these bases are open to public access?