invalid byte sequence for encoding "UNICODE" - Mailing list pgsql-general

From AlannY
Subject invalid byte sequence for encoding "UNICODE"
Date
Msg-id 4888C499.6050109@alanny.ru
Whole thread Raw
Responses Re: invalid byte sequence for encoding "UNICODE"
List pgsql-general
Hi there.

Many times, I'm confronting with that strange problem: invalid byte
sequence for encoding "UNICODE". So, I guess, Postgresql can't allow me
to use some symbols which is not a part of UNICODE. But what is that
symbals?

I'm attaching a screenshot with THAT dead-symbol. As you can see - it's
an unknown symbol in the end of Cyrillic. First of all, I have checked
my data with iconv (iconv -f UTF-8 -t UTF-8 data.txt) and there are no
errors, so, I guess, there are no dead-symbols.

So the question is: is it possible to find a *table* with forbitten
characters for encoding "UNICODE"? If I can get it -> I can kill that
dead-characters in my program ;-)

Thank you.

pgsql-general by date:

Previous
From: "Bob Pawley"
Date:
Subject: cursor
Next
From: Tom Lane
Date:
Subject: Re: invalid byte sequence for encoding "UNICODE"