X-Original-To: pgsql-admin-postgresql.org@localhost.postgresql.org Received: from localhost (av.hub.org [200.46.204.144]) by postgresql.org (Postfix) with ESMTP id 2F0B59DCA02 for ; Tue, 7 Mar 2006 12:07:32 -0400 (AST) Received: from postgresql.org ([200.46.204.71]) by localhost (av.hub.org [200.46.204.144]) (amavisd-new, port 10024) with ESMTP id 52225-07 for ; Tue, 7 Mar 2006 12:07:28 -0400 (AST) 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 CE02B9DC889 for ; Tue, 7 Mar 2006 12:07:27 -0400 (AST) Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1]) by sss.pgh.pa.us (8.13.1/8.13.1) with ESMTP id k27G7Qcb019682; Tue, 7 Mar 2006 11:07:26 -0500 (EST) To: ow cc: pgsql-admin@postgresql.org Subject: Re: New database: SQL_ASCII vs UTF-8 trade-offs In-reply-to: <20060307154859.55607.qmail@web53903.mail.yahoo.com> References: <20060307154859.55607.qmail@web53903.mail.yahoo.com> Comments: In-reply-to ow message dated "Tue, 07 Mar 2006 07:48:59 -0800" Date: Tue, 07 Mar 2006 11:07:26 -0500 Message-ID: <19681.1141747646@sss.pgh.pa.us> From: Tom Lane X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, score=0.112 required=5 tests=[AWL=0.112] X-Spam-Score: 0.112 X-Spam-Level: X-Archive-Number: 200603/70 X-Sequence-Number: 20827 ow writes: > I see... If *ALL* data is in ASCII, is it possible to just update > "pg_database.encoding" to UTF-8 or will I need to recreate the db? It seems risky, but you could probably get away with that as long as the database locale (LC_COLLATE/LC_CTYPE) is "C" ... which is really the only one that's safe with SQL_ASCII anyway ... note that already-started backends will probably fail to notice such a change. regards, tom lane