Received: from localhost (wm.hub.org [200.46.204.128]) by postgresql.org (Postfix) with ESMTP id 925F39FA6B5 for ; Tue, 14 Nov 2006 15:20:35 -0400 (AST) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.204.128]) (amavisd-new, port 10024) with ESMTP id 39763-10 for ; Tue, 14 Nov 2006 19:20:27 +0000 (UTC) X-Greylist: from auto-whitelisted by SQLgrey- Received: from coe.tamu.edu (edsun.coe.tamu.edu [165.91.232.6]) by postgresql.org (Postfix) with ESMTP id F2A539FA5C8 for ; Tue, 14 Nov 2006 15:20:26 -0400 (AST) Received: (from root@localhost) by coe.tamu.edu (8.11.7p2+Sun/8.12.11) id kAEJHDZ00784 for pgsql-admin@postgresql.org; Tue, 14 Nov 2006 13:17:13 -0600 (CST) Received: from coe.tamu.edu (coe.tamu.edu [165.91.232.6]) by coe.tamu.edu (8.11.7p2+Sun/8.12.11) with ESMTP id kAEJFlF00712; Tue, 14 Nov 2006 13:16:01 -0600 (CST) Date: Tue, 14 Nov 2006 13:15:46 -0600 (CST) From: "Ben K." To: "Jim C. Nasby" cc: pgsql-admin@postgresql.org Subject: Re: running initdb on running database In-Reply-To: <20061114171715.GX90133@nasby.net> Message-ID: References: <20061114171715.GX90133@nasby.net> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Virus-Scanned: by AMaViS 0.3.12 X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200611/144 X-Sequence-Number: 23671 On Tue, 14 Nov 2006, Jim C. Nasby wrote: > On Mon, Nov 13, 2006 at 03:10:14PM -0600, Ben K. wrote: >> Admins, >> I'm reading this post: >> http://archives.postgresql.org/pgsql-novice/2005-04/msg00221.php >> Is it possible and safe to run initdb again on a running database to >> change encoding from SQL_ASCII to UTF8? >> Will it affect new databases only or existing databases as well? > Pretty much guaranteed to be unsafe. It's also not possible unless you > hack initdb. > -- > Jim Nasby jim@nasby.net > EnterpriseDB http://enterprisedb.com 512.569.9461 (cell) Thanks. I guess then the next upgrade may be the best opportunity to change the encoding. Regards, Ben K. Developer http://benix.tamu.edu