X-Original-To: pgsql-admin-postgresql.org@localhost.postgresql.org Received: from localhost (unknown [200.46.204.2]) by svr1.postgresql.org (Postfix) with ESMTP id 9BBC7D1B562 for ; Tue, 20 Apr 2004 02:06:07 -0300 (ADT) Received: from svr1.postgresql.org ([200.46.204.71]) by localhost (neptune.hub.org [200.46.204.2]) (amavisd-new, port 10024) with ESMTP id 51990-10 for ; Tue, 20 Apr 2004 02:06:05 -0300 (ADT) Received: from teledns.issi2b.de (telegate.issi2b.de [62.153.140.146]) by svr1.postgresql.org (Postfix) with ESMTP id 2D24CD1B895 for ; Tue, 20 Apr 2004 02:05:59 -0300 (ADT) Received: from notes1.ezi.de (unknown [192.168.150.15]) by teledns.issi2b.de (Secondary Mailpath Linux) with ESMTP id 4C3622328C; Tue, 20 Apr 2004 07:16:10 +0200 (CEST) Received: from dv-08.intern.ezi.de ([192.168.150.109]) by notes1.ezi.de (Lotus Domino Release 5.0.6a) with ESMTP id 2004042007043997:251132 ; Tue, 20 Apr 2004 07:04:39 +0200 Received: by dv-08.intern.ezi.de (Frank sein lokaler Mehlserbe #Postfix on SuSE Linux 8.0 (i386), from userid 578) id 1FEC53BC1DB; Tue, 20 Apr 2004 07:05:51 +0200 (CEST) Date: Tue, 20 Apr 2004 07:05:51 +0200 From: Frank Finner Cc: pgsql-admin@postgresql.org, lloyd@middleware-company.com, eric@middleware-company.com Subject: Re: Going from a DB using SQL_ASCII to UNICODE Message-Id: <20040420070551.385713b2.postgresql@finner.de> In-Reply-To: References: Organization: EZI GmbH X-Mailer: Sylpheed version 0.8.10claws72 (GTK+ 1.2.10; i686-pc-linux-gnu) Mime-Version: 1.0 X-MIMETrack: Itemize by SMTP Server on Prod1/SRV/Haiger/EZI/DE(Release 5.0.6a |January 17, 2001) at 20.04.2004 07:04:39, Serialize by Router on Prod1/SRV/Haiger/EZI/DE(Release 5.0.6a |January 17, 2001) at 20.04.2004 07:04:40, Serialize complete at 20.04.2004 07:04:40 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=US-ASCII X-Virus-Scanned: by amavisd-new at postgresql.org X-Archive-Number: 200404/256 X-Sequence-Number: 13229 Hi, I answered to a similiar problem on the [GENERAL] list a few days ago. In short: You can use "recode" in a pipe between dump and restore like "pg_dump database|recode ascii..utf8|psql newdatabase" to get rid of unicode problems while transferring from a different encoding. Please look at my statements on the[GENERAL] list for the gory details. Regards, Frank. On Mon, 19 Apr 2004 15:44:33 -0400 pgsql-admin-owner@postgresql.org wrote: > > Hi - > > We are running PostgreSQL 7.1.4, and are finally upgrading... to 7.4.2. > > While we do this upgrade, we also want to make create our DB as UNICODE (we > are having problems with SQL_ASCII where we get a bunch of ? marks). > > When we try to import the data from a SQL_ASCII dumped db, into the new > UNICODE db, everything freaks out. > We get errors restoring from dumps that used COPY and with INSERT. > > We also tried to use the 7.4 pg_dump to make sure that it wasn't a problem > with the old pg_dump. > > The errors are: > > - ERROR: missing data for column "noiselevel" > - CONTEXT: COPY messages, line 1: "4393 -1 1441 14147 0 > 2000-10-12 18:30:58-05 EJB Design Questions \N Hi," > - FATAL: invalid frontend message type 60 > - ERROR: invalid byte sequence for encoding "UNICODE": 0xe9616c > > Anyway, if anyone has any recommendations on how to migrate from SQL_ASCII > to UNICODE, with the knowledge that we are going from 7.1 to 7.4 at the same > time.... You will be life-savers! > > Cheers, > > Dion