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 3C9BDD9026 for ; Mon, 10 Oct 2005 09:24:43 -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 44182-01 for ; Mon, 10 Oct 2005 12:24:39 +0000 (GMT) Received: from antivirus.unimo.it (antivirus.unimo.it [155.185.1.3]) by svr1.postgresql.org (Postfix) with ESMTP id 70350D8D8D for ; Mon, 10 Oct 2005 09:24:39 -0300 (ADT) Received: from [155.185.48.190] (fluca.ing.unimo.it [155.185.48.190]) by antivirus.unimo.it (8.12.11/8.12.11) with ESMTP id j9ACOekq018907 for ; Mon, 10 Oct 2005 14:24:40 +0200 Message-ID: <434A5D8E.1000401@infinito.it> Date: Mon, 10 Oct 2005 14:24:46 +0200 From: Luca Ferrari User-Agent: Mozilla Thunderbird 1.0.6 (Windows/20050716) X-Accept-Language: en-us, en MIME-Version: 1.0 To: pgsql-admin@postgresql.org Subject: Re: character problem References: <4349106C.6080206@infinito.it> <434A2792.1070106@infinito.it> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: by amavisd-milter on antivirus (http://amavis.org/) X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, hits=0.516 required=5 tests=[FROM_ENDS_IN_NUMS=0.516] X-Spam-Level: X-Archive-Number: 200510/111 X-Sequence-Number: 19183 Hannes Dorbath's cat, on 10/10/2005 12.08, walking on the keyboard wrote: > OK, so you are not using Unicode. I don't know much about the SQL_ASCII > charset, but I expect it to slightly differ from LATIN1. Type > > SET client_encoding = LATIN1; > > in psql, then SELECT some data containing the chars you have problems > with and see if it is fixed. If not, INSERT a new row with such chars > from psql, SELECT that row again and if the chars look right now, your > other rows are stored invalid in the datebase and you need to convert > them somehow. 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? Moreover, the set client_encoding change is permanent or do I have to configure it in the postgresql.conf file? Thanks, Luca -- Luca Ferrari fluca1978@infinito.it