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 51F37D1E944 for ; Mon, 19 Apr 2004 19:12:55 -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 33843-06 for ; Mon, 19 Apr 2004 19:12:55 -0300 (ADT) Received: from news.hub.org (news.hub.org [200.46.204.72]) by svr1.postgresql.org (Postfix) with ESMTP id BD285D1E95D for ; Mon, 19 Apr 2004 19:12:52 -0300 (ADT) Received: from news.hub.org (news.hub.org [200.46.204.72]) by news.hub.org (8.12.9/8.12.9) with ESMTP id i3JMCqSx018718 for ; Mon, 19 Apr 2004 22:12:52 GMT (envelope-from news@news.hub.org) Received: (from news@localhost) by news.hub.org (8.12.9/8.12.9/Submit) id i3JM18Ap016162 for pgsql-admin@postgresql.org; Mon, 19 Apr 2004 22:01:09 GMT From: CoL X-Newsgroups: comp.databases.postgresql.admin Subject: Re: Going from a DB using SQL_ASCII to UNICODE Date: Tue, 20 Apr 2004 00:02:07 +0200 Organization: Hub.Org Networking Services Lines: 8 Message-ID: References: Reply-To: col@mportal.hu Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Complaints-To: usenet@news.hub.org User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.7b) Gecko/20040316 X-Accept-Language: en-us, en In-Reply-To: To: pgsql-admin@postgresql.org X-Virus-Scanned: by amavisd-new at postgresql.org X-Archive-Number: 200404/263 X-Sequence-Number: 13236 hi, Dion Almaer wrote, On 4/19/2004 21:44: > - ERROR: invalid byte sequence for encoding "UNICODE": 0xe9616c and for this: convert your dump with iconv to unicode, then load it. C.