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 2764BD1D23A for ; Mon, 19 Apr 2004 22:24:29 -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 90809-07 for ; Mon, 19 Apr 2004 22:24:31 -0300 (ADT) Received: from server1070.gisol.com (server1070.gisol.com [216.240.136.190]) by svr1.postgresql.org (Postfix) with ESMTP id 38C8FD1BCB8 for ; Mon, 19 Apr 2004 22:24:27 -0300 (ADT) Received: from h0080c8146f54.ne.client2.attbi.com ([24.128.49.92] helo=crumpet) by server1070.gisol.com with esmtp (Exim 4.24) id 1BFjzt-0002Uq-Oq; Mon, 19 Apr 2004 18:24:25 -0700 From: "Dion Almaer" To: "'Tom Lane'" Cc: , "Lloyd Benson" , "Eric Preston" Subject: Re: Going from a DB using SQL_ASCII to UNICODE Date: Mon, 19 Apr 2004 21:24:25 -0400 Keywords: FIRM MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Mailer: Microsoft Office Outlook, Build 11.0.5510 Thread-Index: AcQmdbMJSIEpSCi1SjWNU14WAnAJRgAAGqvw In-Reply-To: <2263.1082424044@sss.pgh.pa.us> X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165 Message-Id: X-AntiAbuse: This header was added to track abuse, please include it with any abuse report X-AntiAbuse: Primary Hostname - server1070.gisol.com X-AntiAbuse: Original Domain - postgresql.org X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12] X-AntiAbuse: Sender Address Domain - almaer.com X-Virus-Scanned: by amavisd-new at postgresql.org X-Archive-Number: 200404/255 X-Sequence-Number: 13228 Tom, I will try to add "set client_encoding = sql_ascii;" and pray :) Cheers, Dion > -----Original Message----- > From: Tom Lane [mailto:tgl@sss.pgh.pa.us] > Sent: Monday, April 19, 2004 9:21 PM > To: Dion Almaer > Cc: pgsql-admin@postgresql.org; 'Lloyd Benson'; Eric Preston > Subject: Re: [ADMIN] Going from a DB using SQL_ASCII to UNICODE > > "Dion Almaer" writes: > > When we try to import the data from a SQL_ASCII dumped db, into the > > new UNICODE db, everything freaks out. > > I'm no expert on this stuff, but I think what you need to do is add > > set client_encoding = sql_ascii; > > to the top of the dump file. (As of fairly recently, pg_dump > will automatically add such a SET, but I'm pretty sure 7.4.2 won't.) > > If that doesn't help, then what you have is actually not > valid UTF-8 data, and what you'll have to do is figure out > what encoding it's in and specify that instead. If it's in a > mishmash of different encodings, you're in for some pain :-( > > regards, tom lane > >