pg.ddx.io  pgsql-hackers@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Tom Lane <tgl@sss.pgh.pa.us>
To: Tsunakawa, Takayuki <tsunakawa.takay@jp.fujitsu.com>
Cc: 'Tatsuo Ishii' <ishii@sraoss.co.jp>
Cc: pgsql-hackers@postgresql.org <pgsql-hackers@postgresql.org>
Subject: Re: Supporting SJIS as a database encoding
Date: Mon, 05 Sep 2016 23:10:14 -0400
Message-ID: <27598.1473131414@sss.pgh.pa.us> (raw)
In-Reply-To: <0A3221C70F24FB45833433255569204D1F5E6615@G01JPEXMBYT05>
References: <0A3221C70F24FB45833433255569204D1F5E5F9D@G01JPEXMBYT05>
	<20160905.163854.612818171756520492.t-ishii@sraoss.co.jp>
	<0A3221C70F24FB45833433255569204D1F5E602E@G01JPEXMBYT05>
	<9599.1473086835@sss.pgh.pa.us>
	<0A3221C70F24FB45833433255569204D1F5E6615@G01JPEXMBYT05>
List-Unsubscribe: <mailto:majordomo@postgresql.org?body=unsub%20pgsql-hackers>

"Tsunakawa, Takayuki" <tsunakawa.takay@jp.fujitsu.com> writes:
> Using multibyte-functions like mb... to process characters would solve
> the problem?

Well, sure.  The problem is (1) finding all the places that need that
(I'd estimate dozens to hundreds of places in the core code, and then
there's the question of extensions); (2) preventing new
non-multibyte-aware code from being introduced after you've fixed those
places; and (3) the performance penalties you'd take, because a lot of
those places are bottlenecks and it's much cheaper to not worry about
character lengths in an inner loop.

> Isn't the current implementation blocking the support of
> other character sets that have similar characteristics?

Sure, SJIS is not the only encoding that we consider frontend-only.
See

https://www.postgresql.org/docs/devel/static/multibyte.html#MULTIBYTE-CHARSET-SUPPORTED

			regards, tom lane


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



view thread (19+ messages)  latest in thread

Message-ID: <27598.1473131414@sss.pgh.pa.us>
Permalink:  ../27598.1473131414@sss.pgh.pa.us/
Also on:    postgresql.org/message-id/27598.1473131414@sss.pgh.pa.us

 · 

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: pgsql-hackers@postgresql.org
  Cc: tgl@sss.pgh.pa.us, tsunakawa.takay@jp.fujitsu.com, ishii@sraoss.co.jp
  Subject: Re: Supporting SJIS as a database encoding
  In-Reply-To: <27598.1473131414@sss.pgh.pa.us>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox