Received: from malur.postgresql.org ([217.196.149.56])
 by arkaria.postgresql.org with esmtp (Exim 4.80) (envelope-from
 <pgsql-hackers-owner+M234157=pgsql-hackers-arkari@postgresql.org>)
 id 1VNAhJ-0006YF-2t
 for pgsql-hackers@arkaria.postgresql.org; Sat, 21 Sep 2013 00:05:17 +0000
Received: from localhost ([127.0.0.1] helo=postgresql.org)
 by malur.postgresql.org with smtp (Exim 4.80) (envelope-from
 <pgsql-hackers-owner+M234157=pgsql-hackers-arkari@postgresql.org>)
 id 1VNAhI-0002FQ-8G
 for pgsql-hackers@arkaria.postgresql.org; Sat, 21 Sep 2013 00:05:16 +0000
Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29])
 by malur.postgresql.org with esmtp (Exim 4.80)
 (envelope-from <maumau307@gmail.com>) id 1VNAhG-0002F5-H7
 for pgsql-hackers@postgresql.org; Sat, 21 Sep 2013 00:05:14 +0000
Received: from mail-pb0-x229.google.com ([2607:f8b0:400e:c01::229])
 by magus.postgresql.org with esmtp (Exim 4.80)
 (envelope-from <maumau307@gmail.com>)
 id 1VNAhD-00026t-CW; Sat, 21 Sep 2013 00:05:13 +0000
Received: by mail-pb0-f41.google.com with SMTP id rp2so977711pbb.0
 for <multiple recipients>; Fri, 20 Sep 2013 17:05:09 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;
 h=message-id:from:to:cc:references:in-reply-to:subject:date
 :mime-version:content-type:content-transfer-encoding;
 bh=lO+k80a25JUHxNu//zjeIgs7r/H138TapJnotuevyEM=;
 b=jPR3liqfx731SQGB7LwZJO50k3PL+R9ZCbjh4o+lKFqyoe75mG2bPUJv4aCh8X0aPQ
 xTJ4DtgZQh2dkxK1QI0XDF2NA0W5LXVSZckerTea6HFdYktsSpN7wmkS1XB9JFMRvS8w
 fBLgamZGwJfCjQFCc28Y1F0rWX+ma7NS+NMBeFzA3vS7eM3w+RgUW/WF73fPC6GXK9ty
 u8M5dkEYkc1/uOVironyCzytyHoxqnlrOgoGl0Qdw5ZiS3aXp2468q3YX/qIcjzxaGwv
 b5XS1ujcPj3iUHcJDBIqZ1HusuZjxycwFzwNDP+u8VQQwsSCv94q93Tdr8fUNUPCKnF4
 cJTQ==
X-Received: by 10.68.172.3 with SMTP id ay3mr10785590pbc.5.1379721909730;
 Fri, 20 Sep 2013 17:05:09 -0700 (PDT)
Received: from maumau (p6019-ipbfp211sizuokaden.shizuoka.ocn.ne.jp.
 [114.170.213.19])
 by mx.google.com with ESMTPSA id yo2sm21713031pab.8.1969.12.31.16.00.00
 (version=TLSv1 cipher=RC4-SHA bits=128/128);
 Fri, 20 Sep 2013 17:05:08 -0700 (PDT)
Message-ID: <F98A2B6D87404A7D8134F6C50BAACAD5@maumau>
From: "MauMau" <maumau307@gmail.com>
To: "Valentine Gogichashvili" <valgog@gmail.com>,
	<ishii@postgresql.org>
Cc: "Robert Haas" <robertmhaas@gmail.com>, "Tom Lane" <tgl@sss.pgh.pa.us>,
 "Boguk, Maksym" <maksymb@fast.au.fujitsu.com>,
 "Heikki Linnakangas" <hlinnakangas@vmware.com>,
 "PostgreSQL Hackers" <pgsql-hackers@postgresql.org>
References: <A756FAD7EDC2E24F8CAB7E2F3B5375E918E2D5B8@FALEX03.au.fjanz.com>
 <522594E8.2050106@vmware.com>
 <A756FAD7EDC2E24F8CAB7E2F3B5375E918F332A6@FALEX03.au.fjanz.com>
 <904.1378304922@sss.pgh.pa.us> <B1A7485194DE4FDAB8FA781AFB570079@maumau>
 <CA+TgmobWv_96dSfSHv2ZJWSXAD=QTiBEKw-LT359sGArYe+AXQ@mail.gmail.com>
 <B00EACB87A2441069B4EE4DEA6D9282A@maumau>
 <CA+TgmoaT-h5C25LXd1DgfyiW2t9K92eVdVcJHC_1We0JpJFqgg@mail.gmail.com>
 <37B76474BB3149FD841373E12E355851@maumau>
 <CAP93muULVtyd-HQd=h2VOWzaPUrf2Z9efqXDJvmV0Xx3Auj16Q@mail.gmail.com>
In-Reply-To: 
 <CAP93muULVtyd-HQd=h2VOWzaPUrf2Z9efqXDJvmV0Xx3Auj16Q@mail.gmail.com>
Subject: Re: UTF8 national character data type support WIP patch and list of
 open issues.
Date: Sat, 21 Sep 2013 09:07:13 +0900
MIME-Version: 1.0
Content-Type: text/plain; format=flowed; charset="utf-8"; reply-type=original
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Windows Mail 6.0.6002.18197
X-MimeOLE: Produced By Microsoft MimeOLE V6.0.6002.18463
X-Pg-Spam-Score: -1.3 (-)
List-Archive: <http://archives.postgresql.org/pgsql-hackers>
List-Help: <mailto:majordomo@postgresql.org?body=help>
List-ID: <pgsql-hackers.postgresql.org>
List-Owner: <mailto:pgsql-hackers-owner@postgresql.org>
List-Post: <mailto:pgsql-hackers@postgresql.org>
List-Subscribe: <mailto:majordomo@postgresql.org?body=sub%20pgsql-hackers>
List-Unsubscribe: <mailto:majordomo@postgresql.org?body=unsub%20pgsql-hackers>
X-Mailing-List: pgsql-hackers
Precedence: bulk
Sender: pgsql-hackers-owner@postgresql.org

From: "Valentine Gogichashvili" <valgog@gmail.com>
> the whole NCHAR appeared as hack for the systems, that did not have it 
> from
> the beginning. It would not be needed, if all the text would be magically
> stored in UNICODE or UTF from the beginning and idea of character would be
> the same as an idea of a rune and not a byte.

I guess so, too.


> PostgreSQL has a very powerful possibilities for storing any kind of
> encoding. So maybe it makes sense to add the ENCODING as another column
> property, the same way a COLLATION was added?

Some other people in this community suggested that.  ANd the SQL standard 
suggests the same -- specifying a character encoding for each column: 
CHAR(n) CHARASET SET ch.


> Text operations should work automatically, as in memory all strings will 
> be
> converted to the database encoding.
>
> This approach will also open a possibility to implement custom ENCODINGs
> for the column data storage, like snappy compression or even BSON, gobs or
> protbufs for much more compact type storage.

Thanks for your idea that sounds interesting, although I don't understand 
that well.

Regards
MauMau



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