X-Original-To: pgsql-admin-postgresql.org@localhost.postgresql.org Received: from localhost (mx1.hub.org [200.46.208.251]) by postgresql.org (Postfix) with ESMTP id 29F959FA5F0 for ; Wed, 31 May 2006 11:43:33 -0300 (ADT) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.208.251]) (amavisd-new, port 10024) with ESMTP id 44181-04 for ; Wed, 31 May 2006 11:43:23 -0300 (ADT) X-Greylist: from auto-whitelisted by SQLgrey- Received: from sss.pgh.pa.us (sss.pgh.pa.us [66.207.139.130]) by postgresql.org (Postfix) with ESMTP id C4BDF9FA5DD for ; Wed, 31 May 2006 11:43:23 -0300 (ADT) Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1]) by sss.pgh.pa.us (8.13.6/8.13.6) with ESMTP id k4VEhEUV012253; Wed, 31 May 2006 10:43:14 -0400 (EDT) To: Michael Kichanov cc: pgsql-admin@postgresql.org Subject: Re: Changing the encoding of the database on the fly In-reply-to: <200605311335.RAA11979@mix.inar.ru> References: <200605311335.RAA11979@mix.inar.ru> Comments: In-reply-to Michael Kichanov message dated "Wed, 31 May 2006 17:35:40 +0400" Date: Wed, 31 May 2006 10:43:14 -0400 Message-ID: <12252.1149086594@sss.pgh.pa.us> From: Tom Lane X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200605/430 X-Sequence-Number: 21962 Michael Kichanov writes: > Can i change the encoding of the database with "update pg_database set encoding= where datname=" > without any problem with DB integrity? No. That's not going to magically fix your data to be correct in the new encoding. regards, tom lane