Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtp (Exim 4.80) (envelope-from ) id 1ZqmFX-0000ce-2u for pgsql-translators@arkaria.postgresql.org; Mon, 26 Oct 2015 18:12:03 +0000 Received: from localhost ([127.0.0.1] helo=postgresql.org) by malur.postgresql.org with smtp (Exim 4.84) (envelope-from ) id 1ZqmFW-0001AR-9t for pgsql-translators@arkaria.postgresql.org; Mon, 26 Oct 2015 18:12:02 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.84) (envelope-from ) id 1ZqmFU-00016i-RK; Mon, 26 Oct 2015 18:12:00 +0000 Received: from sss.pgh.pa.us ([66.207.139.130]) by magus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.84) (envelope-from ) id 1ZqmFS-00023F-Gd; Mon, 26 Oct 2015 18:12:00 +0000 Received: from sss1.sss.pgh.pa.us (localhost [127.0.0.1]) by sss.pgh.pa.us (8.14.4/8.14.4) with ESMTP id t9QIBust031571; Mon, 26 Oct 2015 14:11:56 -0400 From: Tom Lane To: fortin.christian@videotron.ca cc: pgsql-translators@postgresql.org, pgsql-hackers@postgresql.org Subject: Re: [HACKERS] UTF-32 support in PostgreSQL ? In-reply-to: <7310a455c4445.562ac2f1@videotron.ca> References: <7310b292c0558.562afaab@videotron.ca> <7310dc30c2b71.562afae8@videotron.ca> <7390a359c6c9c.562afb25@videotron.ca> <7310a455c4445.562ac2f1@videotron.ca> Comments: In-reply-to fortin.christian@videotron.ca message dated "Fri, 23 Oct 2015 23:29:53 -0400" Date: Mon, 26 Oct 2015 14:11:56 -0400 Message-ID: <31570.1445883116@sss.pgh.pa.us> X-Pg-Spam-Score: -1.9 (-) List-Archive: List-Help: List-ID: List-Owner: List-Post: List-Subscribe: List-Unsubscribe: X-Mailing-List: pgsql-translators Precedence: bulk Sender: pgsql-translators-owner@postgresql.org fortin.christian@videotron.ca writes: > Is PostgreSQL support UNICODE UTF-32 characters ? There's no particular intention of supporting the UTF32 representation inside the database. We do support UTF8 representation of the entire Unicode character set. You can transcode to and from UTF32 easily enough, if you have a client application that prefers to work in that representation. regards, tom lane -- Sent via pgsql-translators mailing list (pgsql-translators@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-translators