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 3FFC79DC84D for ; Tue, 7 Mar 2006 10:37:51 -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 24233-10 for ; Tue, 7 Mar 2006 10:37:51 -0400 (AST) X-Greylist: from auto-whitelisted by SQLgrey- Received: from gauss.credativ.com (ipx11302.ipxserver.de [212.112.227.254]) by postgresql.org (Postfix) with ESMTP id 005499DC845 for ; Tue, 7 Mar 2006 10:37:44 -0400 (AST) Received: from bell.credativ.de (p50897224.dip.t-dialin.net [80.137.114.36]) (using TLSv1 with cipher EXP1024-RC4-SHA (56/128 bits)) (No client certificate requested) by gauss.credativ.com (Postfix) with ESMTP id 3053DD75F1; Tue, 7 Mar 2006 15:37:49 +0100 (CET) From: Peter Eisentraut To: pgsql-admin@postgresql.org Subject: Re: New database: SQL_ASCII vs UTF-8 trade-offs Date: Tue, 7 Mar 2006 15:38:11 +0100 User-Agent: KMail/1.8.3 Cc: ow References: <20060307140824.73656.qmail@web53902.mail.yahoo.com> In-Reply-To: <20060307140824.73656.qmail@web53902.mail.yahoo.com> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 8bit Content-Disposition: inline Message-Id: <200603071538.12028.peter_e@gmx.net> X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, score=0.104 required=5 tests=[AWL=0.104] X-Spam-Score: 0.104 X-Spam-Level: X-Archive-Number: 200603/62 X-Sequence-Number: 20819 Am Dienstag, 7. März 2006 15:08 schrieb ow: > Are there any negative effects related to the selection of UTF-8 over > SQL_ASCII (e.g. size of the database, sort/like/group issues, etc)? If you're only planning to store ASCII data, choosing UTF-8 will not cause any additional problems. But obviously you're more future-proof that way. -- Peter Eisentraut http://developer.postgresql.org/~petere/