From: | Alvaro Herrera <alvherre(at)dcc(dot)uchile(dot)cl> |
---|---|
To: | Carlos Moreno <moreno(at)mochima(dot)com> |
Cc: | pgsql-general(at)postgresql(dot)org |
Subject: | Re: Encoding-related errors when moving from 7.3 to 8.0.1 |
Date: | 2005-03-20 04:35:49 |
Message-ID: | 20050320043549.GB25831@dcc.uchile.cl |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On Sat, Mar 19, 2005 at 05:25:46PM -0500, Carlos Moreno wrote:
Carlos,
> The error reads like:
>
> psql:db_backup.sql:1548: ERROR: invalid byte sequence for encoding
> "UNICODE": 0xe12020
> CONTEXT: COPY country, line 5, column namespanish:
> "Canad? "
Hmm. The sequence looks like latin1 interpreted as utf8. This seems
the inverse of the problem reported (and solved) here
http://archives.postgresql.org/pgsql-es-ayuda/2005-03/msg00491.php
Maybe you should try sticking a
SET client_encoding TO latin1;
at the beggining of the dump file.
Why are you using CHAR(n) fields anyway? It should probably be better
if you used VARCHAR(n) ...
--
Alvaro Herrera (<alvherre[(at)]dcc(dot)uchile(dot)cl>)
"El destino baraja y nosotros jugamos" (A. Schopenhauer)
From | Date | Subject | |
---|---|---|---|
Next Message | Bruno Wolff III | 2005-03-20 05:32:20 | Re: Using sequence name depending on other column |
Previous Message | Edward Macnaghten | 2005-03-20 00:21:00 | Re: MS Access to PostgreSQL |