RE: [GENERAL] Query failed: ERROR: character with byte sequence 0xc2 0x96 in encoding "UTF8" has no equivalent in encoding "WIN1250" - Mailing list pgsql-general

From NTPT
Subject RE: [GENERAL] Query failed: ERROR: character with byte sequence 0xc2 0x96 in encoding "UTF8" has no equivalent in encoding "WIN1250"
Date
Msg-id 3gP.DhxV.3vo4DamXUUM.1MLRuD@seznam.cz
Whole thread Raw
In response to Query failed: ERROR: character with byte sequence 0xc2 0x96 in encoding "UTF8" has no equivalent in encoding "WIN1250"  (NTPT <NTPT@seznam.cz>)
Responses Re: Query failed: ERROR: character with byte sequence 0xc2 0x96 in encoding "UTF8" has no equivalent in encoding "WIN1250"
List pgsql-general
but how to update affected columns ? error message does not  provide single  clue ( at least row name)

And dump-restore ?  It  do not underestand how it could help.. dumped as unicode  restore as unicode = I am at the same point ... dumping as latin2 and restore to utf8 will end with the some errors..  I suspect

---------- Původní zpráva ----------
Od: Albe Laurenz <laurenz.albe@wien.gv.at>
Komu: 'NTPT *EXTERN*' <NTPT@seznam.cz>
Datum: 25. 11. 2015 14:47:46
Předmět: RE: [GENERAL] Query failed: ERROR: character with byte sequence 0xc2 0x96 in encoding "UTF8" has no equivalent in encoding "WIN1250"

NTPT wrote:
> but how to solve this in existing database ?

Either update all affected columns in the source database
or edit the database dump...

Yours,
Laurenz Albe

pgsql-general by date:

Previous
From: Stephen Frost
Date:
Subject: Re: "trust" authentication in pg_hba.conf
Next
From: Bruce Momjian
Date:
Subject: Re: Problems with pg_upgrade after change of unix user running db.