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 726DA9DC840 for ; Tue, 7 Mar 2006 10:08:24 -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 16275-10 for ; Tue, 7 Mar 2006 10:08:27 -0400 (AST) X-Greylist: from auto-whitelisted by SQLgrey- Received: from web53902.mail.yahoo.com (web53902.mail.yahoo.com [206.190.36.212]) by postgresql.org (Postfix) with SMTP id F15AB9DCBE4 for ; Tue, 7 Mar 2006 10:08:20 -0400 (AST) Received: (qmail 73658 invoked by uid 60001); 7 Mar 2006 14:08:24 -0000 DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com; h=Message-ID:Received:Date:From:Subject:To:MIME-Version:Content-Type:Content-Transfer-Encoding; b=2Jl60mIts6PjcADcJaIFRN1hTbj8JwBmjV2bHg5iVg4xfUwdc5mnIrXAnV5+n0WYpiFTvSJLkwtXywHZfij2yTdtxsxq3sFylvJ3IpgixjIw8LthghcMeKeno4l5DUCSJX0mlnvgiMCC6EgeLZIxFBqUYtinLPVLDJfYmieFsIM= ; Message-ID: <20060307140824.73656.qmail@web53902.mail.yahoo.com> Received: from [24.188.184.164] by web53902.mail.yahoo.com via HTTP; Tue, 07 Mar 2006 06:08:24 PST Date: Tue, 7 Mar 2006 06:08:24 -0800 (PST) From: ow Subject: New database: SQL_ASCII vs UTF-8 trade-offs To: pgsql-admin@postgresql.org MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, score=1.138 required=5 tests=[AWL=-0.220, DNS_FROM_RFC_ABUSE=0.479, DNS_FROM_RFC_WHOIS=0.879] X-Spam-Score: 1.138 X-Spam-Level: * X-Archive-Number: 200603/61 X-Sequence-Number: 20818 "PostgreSQL 8.1.0 on i486-pc-linux-gnu, compiled by GCC cc (GCC) 4.0.3 20051111 (prerelease) (Debian 4.0.2-4)" Hi, Am having some doubts whether a new db should be with SQL_ASCII or UTF-8 encoding. We expect ALL of our data to be ASCII. At the same time, I guess, it's possible that some user may decide to get creative and enter, for example, his own name with non-ASCII chars. So, it seems that UTF-8 would be a better choise even if we plan to store only ASCII data (a lot of ASCII data though). 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)? Thanks in advance --------------------------------------------------------------------------- __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com