Re: Re: [NOVICE] Problems with ñ and tildes / CSV import problems in PostgreSQL 9.1

Ken Benson <ken@infowerks.com> writes:
> So - the problem may be that /*truly**0x e1 73 71*/ is not a valid UTF-8
> character in the current iteration of PostgreSQL - or at all.

Of course it isn't, which is why Postgres is complaining.  Presumably
what that data really is is three characters (looks like "�sq") in
LATIN1.  But Postgres is trying to interpret it in UTF8.  As mentioned
upthread, the solution is to adjust the client_encoding setting before
running the COPY command.

            regards, tom lane