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

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Zach Seaman <znseaman(at)gmail(dot)com>
Cc: Ken Benson <ken(at)infowerks(dot)com>, "pgsql-novice(at)postgresql(dot)org" <pgsql-novice(at)postgresql(dot)org>
Subject: Re: Re: [NOVICE] Re: [NOVICE] Problems with ñ and tildes / CSV import problems in PostgreSQL 9.1
Date: 2013-02-07 17:51:15
Message-ID: 15735.1360259475@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general pgsql-novice

Zach Seaman <znseaman(at)gmail(dot)com> writes:
> 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]

No, the client encoding needs to be LATIN1 to read this file.

regards, tom lane

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Tom Lane 2013-02-07 17:59:08 Re: feature requests (possibly interested in working on this): functional foreign keys
Previous Message Zach Seaman 2013-02-07 17:05:19 Re: [NOVICE] Re: [NOVICE] Problems with ñ and tildes / CSV import problems in PostgreSQL 9.1

Browse pgsql-novice by date

  From Date Subject
Next Message Zach Seaman 2013-02-07 17:59:08 Re: [NOVICE] Re: [NOVICE] Re: [NOVICE] Problems with ñ and tildes / CSV import problems in PostgreSQL 9.1
Previous Message Nipuna 2013-02-07 17:39:59 Finding the no of files and directories in a path