Message-ID: <1380077397.1440.25.camel@vanquo.pezone.net>
Subject: Re: UTF8 national character data type support WIP patch
 and list of open issues.
From: Peter Eisentraut <peter_e@gmx.net>
To: MauMau <maumau307@gmail.com>
Cc: robertmhaas@gmail.com, Tatsuo Ishii <ishii@postgresql.org>,
 tgl@sss.pgh.pa.us, maksymb@fast.au.fujitsu.com, hlinnakangas@vmware.com,
 pgsql-hackers@postgresql.org
Date: Tue, 24 Sep 2013 22:49:57 -0400
In-Reply-To: <7DCFAE8265254605840917B35EEF09F1@maumau>
References: 
 <CA+TgmobWv_96dSfSHv2ZJWSXAD=QTiBEKw-LT359sGArYe+AXQ@mail.gmail.com>
 <20130920.085853.1628917054830864151.t-ishii@sraoss.co.jp>
 <CA+TgmoZEy=pt2B5D+nuPAib7KvhNoBgRGYRWnkS4pyrqfcdYHQ@mail.gmail.com>
 <20130922.072952.1977066018971837040.t-ishii@sraoss.co.jp>
 <D0A2FE73E8354EDCBEE56EC79268CA4E@maumau> <5240B212.8040307@gmx.net>
 <7DCFAE8265254605840917B35EEF09F1@maumau>
Content-Type: text/plain; charset="UTF-8"
Mime-Version: 1.0
Content-Transfer-Encoding: 7bit
Precedence: bulk
Sender: pgsql-hackers-owner@postgresql.org

On Tue, 2013-09-24 at 21:04 +0900, MauMau wrote:
> "4. I guess some users really want to continue to use ShiftJIS or EUC_JP for
> database encoding, and use NCHAR for a limited set of columns to store
> international text in Unicode:
> - to avoid code conversion between the server and the client for performance
> - because ShiftJIS and EUC_JP require less amount of storage (2 bytes for
> most Kanji) than UTF-8 (3 bytes)
> This use case is described in chapter 6 of "Oracle Database Globalization
> Support Guide"."

But your proposal wouldn't address the first point, because data would
have to go client -> server -> NCHAR.

The second point is valid, but it's going to be an awful amount of work
for that limited result.


-- 
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers