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 1550DD9AA4 for ; Mon, 10 Oct 2005 04:35:52 -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 38913-03 for ; Mon, 10 Oct 2005 07:35:47 +0000 (GMT) Received: from news.hub.org (news.hub.org [200.46.204.72]) by svr1.postgresql.org (Postfix) with ESMTP id A228DD9B02 for ; Mon, 10 Oct 2005 04: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 j9A7ZjVX042588 for ; Mon, 10 Oct 2005 07:35:45 GMT (envelope-from news@news.hub.org) Received: (from news@localhost) by news.hub.org (8.13.1/8.13.1/Submit) id j9A7S2VC015310 for pgsql-admin@postgresql.org; Mon, 10 Oct 2005 07:28:02 GMT (envelope-from news) From: Hannes Dorbath X-Newsgroups: pgsql.admin Subject: Re: character problem Date: Mon, 10 Oct 2005 09:28:18 +0200 Organization: Hub.Org Networking Services Lines: 32 Message-ID: References: <4349106C.6080206@infinito.it> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 8bit X-Complaints-To: usenet@news.hub.org User-Agent: Thunderbird 1.4 (Windows/20050908) In-Reply-To: <4349106C.6080206@infinito.it> To: pgsql-admin@postgresql.org X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, hits=-2.46 required=5 tests=[ALL_TRUSTED=-2.82, AWL=0.360] X-Spam-Level: X-Archive-Number: 200510/101 X-Sequence-Number: 19173 > like "èòéàùì", the string is stored in the database with other characters instead of those digited by the user. Well, how does `èòéàùì' look like in your database? Like `èòéà ùì'? In that case you most probably have initialized your cluster with an UTF-8 locale while not using a / the correct client encoding. You can check your database encoding with \l in psql. If your perl clients don't handle UTF-8, just set a client encoding for them. SET client_encoding = LATIN1; for example. The client encoding can be set for a user, as default in postgresql.conf, interactive using the command above and maybe other ways. > And most important, is it possible to adjust the already inserted strings without having to update the tables? Your first need to deside what is wrong at all -- the way the servers stores your chars, or the way your client displays them. > is it possible to change the locale settings thus the strings in the database are displayed rightly? The client encoding can be set anytime, to change the cluster LOCALE or database encoding you need to initDB + dump and restore AFAIK. -- Regards, Hannes Dorbath