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 D8E6AD1B49B for ; Mon, 19 Apr 2004 22:20:47 -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 88799-06 for ; Mon, 19 Apr 2004 22:20:49 -0300 (ADT) Received: from sss.pgh.pa.us (sss.pgh.pa.us [66.207.139.130]) by svr1.postgresql.org (Postfix) with ESMTP id EAC3DD1B515 for ; Mon, 19 Apr 2004 22:20:45 -0300 (ADT) Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1]) by sss.pgh.pa.us (8.12.11/8.12.11) with ESMTP id i3K1KioP002264; Mon, 19 Apr 2004 21:20:44 -0400 (EDT) To: "Dion Almaer" Cc: pgsql-admin@postgresql.org, "'Lloyd Benson'" , "Eric Preston" Subject: Re: Going from a DB using SQL_ASCII to UNICODE In-reply-to: References: Comments: In-reply-to "Dion Almaer" message dated "Mon, 19 Apr 2004 15:44:33 -0400" Date: Mon, 19 Apr 2004 21:20:44 -0400 Message-ID: <2263.1082424044@sss.pgh.pa.us> From: Tom Lane X-Virus-Scanned: by amavisd-new at postgresql.org X-Archive-Number: 200404/254 X-Sequence-Number: 13227 "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