X-Original-To: pgsql-admin-postgresql.org@localhost.postgresql.org Received: from localhost (av.hub.org [200.46.204.144]) by svr1.postgresql.org (Postfix) with ESMTP id B8203D993F for ; Mon, 10 Oct 2005 10:35:50 -0300 (ADT) Received: from svr1.postgresql.org ([200.46.204.71]) by localhost (av.hub.org [200.46.204.144]) (amavisd-new, port 10024) with ESMTP id 48632-03 for ; Mon, 10 Oct 2005 13:35:46 +0000 (GMT) Received: from news.hub.org (news.hub.org [200.46.204.72]) by svr1.postgresql.org (Postfix) with ESMTP id A3181D966C for ; Mon, 10 Oct 2005 10:35:48 -0300 (ADT) Received: from news.hub.org (news.hub.org [200.46.204.72]) by news.hub.org (8.13.1/8.13.1) with ESMTP id j9ADZkbe073066 for ; Mon, 10 Oct 2005 13:35:46 GMT (envelope-from news@news.hub.org) Received: (from news@localhost) by news.hub.org (8.13.1/8.13.1/Submit) id j9ADOMI8034838 for pgsql-admin@postgresql.org; Mon, 10 Oct 2005 13:24:22 GMT (envelope-from news) From: Hannes Dorbath X-Newsgroups: pgsql.admin Subject: Re: character problem Date: Mon, 10 Oct 2005 15:24:42 +0200 Organization: Hub.Org Networking Services Lines: 20 Message-ID: References: <4349106C.6080206@infinito.it> <434A2792.1070106@infinito.it> <434A5D8E.1000401@infinito.it> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Complaints-To: usenet@news.hub.org User-Agent: Thunderbird 1.4 (Windows/20050908) In-Reply-To: <434A5D8E.1000401@infinito.it> To: pgsql-admin@postgresql.org X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, hits=-2.424 required=5 tests=[ALL_TRUSTED=-2.82, AWL=0.396] X-Spam-Level: X-Archive-Number: 200510/112 X-Sequence-Number: 19184 On 10.10.2005 14:24, Luca Ferrari wrote: > The old rows are still displayed in a bad format, the newly inserted one > is instead shown rightly. Also data in pg_dump present wrong strings, > thus any suggestion about how to reconvert already inserted data? It should be possible to convert it with an intentionally "wrong" client_encoding and one or two reloads, but I don't have the time ATM to think out how to do it exactly, maybe someone else can help in the meantime. > Moreover, the set client_encoding change is permanent or do I have to > configure it in the postgresql.conf file? No it's for the running session only. Set it global in postgresql.conf, for each user or just fire "SET client_encoding = LATIN1;" as first query in your scripts. -- Regards, Hannes Dorbath