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

I think the problem may be that specific character translation.

The chart I typically use is here: http://www.utf8-chartable.de/unicode-utf8-table.pl

The 'valid' UTF-8 codes jump from 0x e0 bf bf (at the bottom of this page: http://www.utf8-chartable.de/unicode-utf8-table.pl?start=3840 )
To: 0x e1 80 80 (at the top of this page: http://www.utf8-chartable.de/unicode-utf8-table.pl?start=4096

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.

Jut my thoughts.

Ken

On Wed, Feb 6, 2013 at 7:56 PM, Zach Seaman <znseaman@gmail.com> wrote:

I'm fairly new to PostgreSQL 9.1 but I need it, so here I am.

This a similar question to this one, so I have encoded a database with
LATIN-1 as suggested but can't copy a CSV file into a table within the
database.

well, that mail is from 2005... what version of postgres are you running at?

ERROR: invalid byte sequence for encoding "UTF8": 0xe17371

run:

SET client_encoding TO UTF8;

before running the copy command, or maybe set to LATIN1