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

I changed from LATIN1, set my database to UTF8, and my client_encoding is
UTF8.

ERROR: invalid byte sequence for encoding "UTF8": 0xe17320
ás[space]

Is it a trial and error type problem now?

On Thu, Feb 7, 2013 at 10:15 AM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:

> Ken Benson <ken(at)infowerks(dot)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
>
>
> --
> Sent via pgsql-novice mailing list (pgsql-novice(at)postgresql(dot)org)
> To make changes to your subscription:
> http://www.postgresql.org/mailpref/pgsql-novice
>

--
*Zach Seaman****
GIS Expert, IRRI-México*
*Master of Regional & Community Planning
*
*m 55.2247.1740 (México)
m 01.913.4860.832 (U.S.)
*