Received: from maia.hub.org (maia-2.hub.org [200.46.204.251]) by mail.postgresql.org (Postfix) with ESMTP id DD58AB5DC57 for ; Wed, 10 Aug 2011 15:42:55 -0300 (ADT) Received: from mail.postgresql.org ([200.46.204.86]) by maia.hub.org (mx1.hub.org [200.46.204.251]) (amavisd-maia, port 10024) with ESMTP id 74559-01-5 for ; Wed, 10 Aug 2011 18:42:49 +0000 (UTC) X-Greylist: from auto-whitelisted by SQLgrey-1.7.6 Received: from gw.wicourts.gov (gwmta.wicourts.gov [165.219.244.99]) by mail.postgresql.org (Postfix) with ESMTP id 78E09B5DD1A for ; Wed, 10 Aug 2011 15:42:36 -0300 (ADT) Received: from Courts-MTA by gw.wicourts.gov with Novell_GroupWise; Wed, 10 Aug 2011 13:42:35 -0500 Message-Id: <4E428AC1020000250003FD63@gw.wicourts.gov> X-Mailer: Novell GroupWise Internet Agent 8.0.1 Date: Wed, 10 Aug 2011 13:42:25 -0500 From: "Kevin Grittner" To: "Mridul Mathew" , Cc: , 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: Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Content-Disposition: inline X-Virus-Scanned: Maia Mailguard 1.0.1 X-Spam-Status: No, hits=-2.711 tagged_above=-10 required=5 tests=BAYES_00=-1.9, RP_MATCHES_RCVD=-0.811 X-Spam-Level: X-Archive-Number: 201108/90 X-Sequence-Number: 38077 Mridul Mathew wrote: > From: *Craig Ringer* >> A 30-second Google search turned up this: >> >> http://decipherinfosys.wordpress.com/2007/01/28/difference-between-utf8-and-al32utf8-character-sets-in-oracle/ > If supplementary characters are inserted in a UTF8 database, they > will be treated as 2 separate undefined characters, occupying 6 > bytes in storage. Oracle recommends using al32utf8 for any newly > defined supplementary characters. > > Does PostgreSQL make a distinction within Unicode in a similar > fashion? It sounds as though Oracle initially failed to properly implement the UTF-8 character encoding scheme, but rather than fix the broken scheme they created an alternative. So far as I know, PostgreSQL should be using proper UTF-8 encoding if you ask for it, without any special gyrations. -Kevin