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 10:47:15 -0400
Message-ID: <9599.1473086835@sss.pgh.pa.us> (raw)
In-Reply-To: <0A3221C70F24FB45833433255569204D1F5E602E@G01JPEXMBYT05>
References: <0A3221C70F24FB45833433255569204D1F5E5F9D@G01JPEXMBYT05>
<20160905.163854.612818171756520492.t-ishii@sraoss.co.jp>
<0A3221C70F24FB45833433255569204D1F5E602E@G01JPEXMBYT05>
List-Unsubscribe: <mailto:majordomo@postgresql.org?body=unsub%20pgsql-hackers>
"Tsunakawa, Takayuki" <tsunakawa.takay@jp.fujitsu.com> writes:
> Before digging into the problem, could you share your impression on
> whether PostgreSQL can support SJIS? Would it be hopeless?
I think it's pretty much hopeless. Even if we were willing to make every
bit of code that looks for '\' and other specific at-risk characters
multi-byte aware (with attendant speed penalties), we could expect that
third-party extensions would still contain vulnerable code. More, we
could expect that new bugs of the same ilk would get introduced all the
time. Many such bugs would amount to security problems. So the amount of
effort and vigilance required seems out of proportion to the benefits.
Most of the recent discussion about allowed backend encodings has run
more in the other direction, ie, "why don't we disallow everything but
UTF8 and get rid of all the infrastructure for multiple backend
encodings?". I'm not personally in favor of that, but there are very
few hackers who want to add any more overhead in this area.
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
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: <9599.1473086835@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