Received: from maia.hub.org (maia-5.hub.org [200.46.204.29]) by mail.postgresql.org (Postfix) with ESMTP id 84819B5DBF1 for ; Wed, 10 Aug 2011 10:55:58 -0300 (ADT) Received: from mail.postgresql.org ([200.46.204.86]) by maia.hub.org (mx1.hub.org [200.46.204.29]) (amavisd-maia, port 10024) with ESMTP id 77259-02 for ; Wed, 10 Aug 2011 13:55:52 +0000 (UTC) X-Greylist: from auto-whitelisted by SQLgrey-1.7.6 Received: from mail-vx0-f174.google.com (mail-vx0-f174.google.com [209.85.220.174]) by mail.postgresql.org (Postfix) with ESMTP id 70D59B5DBE4 for ; Wed, 10 Aug 2011 10:55:52 -0300 (ADT) Received: by vxi9 with SMTP id 9so827227vxi.19 for ; Wed, 10 Aug 2011 06:55:52 -0700 (PDT) Received: by 10.52.115.4 with SMTP id jk4mr8969156vdb.410.1312984552472; Wed, 10 Aug 2011 06:55:52 -0700 (PDT) Received: from [10.1.1.8] (124-169-181-228.dyn.iinet.net.au [124.169.181.228]) by mx.google.com with ESMTPS id gi16sm465538vcb.1.2011.08.10.06.55.49 (version=SSLv3 cipher=OTHER); Wed, 10 Aug 2011 06:55:51 -0700 (PDT) Message-ID: <4E428DE0.8000606@ringerc.id.au> Date: Wed, 10 Aug 2011 21:55:44 +0800 From: Craig Ringer User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:5.0) Gecko/20110624 Thunderbird/5.0 MIME-Version: 1.0 To: Mridul Mathew CC: rajeshwarbharathi@gmail.com, pgsql-admin@postgresql.org Subject: Re: FW: Character set equivalent for AL32UTF8 References: <0149564b-0eea-4ed9-8521-0ab6efec2a4d@glegroupsg2000goo.googlegroups.com> <4E422305.6070404@ringerc.id.au> <8491208A5EFFB84A841235D93FDAC98E76DBEDFD@EXCHANGE.fiberlink.local> In-Reply-To: Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: Maia Mailguard 1.0.1 X-Spam-Status: No, hits=-1.9 tagged_above=-10 required=5 tests=BAYES_00=-1.9 X-Spam-Level: X-Archive-Number: 201108/77 X-Sequence-Number: 38064 On 10/08/2011 4:07 PM, Mridul Mathew wrote: > Does PostgreSQL make a distinction within Unicode in a similar fashion? No. > We have not tested our Oracle al32utf8 databases on PostgreSQL, but > while creating databases in PostgreSQL, we see UTF8 as an option, but > not al32. al32utf8 is Oracle specific and doesn't seem to be defined anywhere else. What _application_ _level_ impact does this have for you? What changes do your apps expect to see in their use of or communication with the database? I strongly suggest that you _test_ this in Pg and see. -- Craig Ringer