View Single Post

   
  #2 (permalink)  
Old 04-08-2008, 08:07 PM
Alvaro Herrera
 
Posts: n/a
Default Re: Encoding-related errors when moving from 7.3 to 8.0.1

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...3/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[@]dcc.uchile.cl>)
"El destino baraja y nosotros jugamos" (A. Schopenhauer)

---------------------------(end of broadcast)---------------------------
TIP 7: don't forget to increase your free space map settings

Reply With Quote