From: | Gurjeet Singh <gurjeet(at)singh(dot)im> |
---|---|
To: | Zach Seaman <znseaman(at)gmail(dot)com> |
Cc: | pgsql-novice(at)postgresql(dot)org |
Subject: | Re: [NOVICE] Problems with ñ and tildes / CSV import problems in PostgreSQL 9.1 |
Date: | 2013-02-07 03:12:43 |
Message-ID: | CABwTF4Vxit=oVytbs-=_EHac8AYgxkPYZP=8FAX9eTQ_wV_MaQ@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general pgsql-novice |
On Wed, Feb 6, 2013 at 7:56 PM, Zach Seaman <znseaman(at)gmail(dot)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<http://www.postgresql.org/message-id/4dda42060512140509xe8b130as@mail.gmail.com>,
> so I have encoded a database with LATIN-1 as suggested but can't copy a CSV
> file into a table within the database.
>
> ERROR: invalid byte sequence for encoding "UTF8": 0xe17371
>
> Googling doesn't get me anywhere and I am working with Spanish characters.
>
I think the data in your CSV file should match the client_encoding
parameter.
What is your client_encoding parameter set to?
show client_encoding;
--
Gurjeet Singh
From | Date | Subject | |
---|---|---|---|
Next Message | Michael Harris | 2013-02-07 06:24:19 | Re: Hot Standby has PANIC: WAL contains references to invalid pages |
Previous Message | Gurjeet Singh | 2013-02-07 03:00:28 | Re: [HACKERS] function for setting/getting same timestamp during whole transaction |
From | Date | Subject | |
---|---|---|---|
Next Message | James David Smith | 2013-02-07 12:05:10 | Re: Installation 8.4 > 9.1 |
Previous Message | Zach Seaman | 2013-02-07 00:56:29 | Problems with ñ and tildes / CSV import problems in PostgreSQL 9.1 |