Postgres Pro
Downloads
Home   >   mailing lists

Re: chr() is still too loose about UTF8 code points - Mailing list pgsql-hackers

From Noah Misch
Subject Re: chr() is still too loose about UTF8 code points
Date
Msg-id 20140516173909.GA8804@tornado.leadboat.com
Whole thread Raw
In response to chr() is still too loose about UTF8 code points  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: chr() is still too loose about UTF8 code points  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
Tree view 
On Fri, May 16, 2014 at 11:05:08AM -0400, Tom Lane wrote:
> I think this probably means we need to change chr() to reject code points
> above 10ffff.  Should we back-patch that, or just do it in HEAD?

The compatibility risks resemble those associated with the fixes for bug
#9210, so I recommend HEAD only:

http://www.postgresql.org/message-id/flat/20140220043940.GA3064539@tornado.leadboat.com

-- 
Noah Misch
EnterpriseDB                                 http://www.enterprisedb.com

pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: chr() is still too loose about UTF8 code points
Next
From: Tom Lane
Date:
Subject: Re: chr() is still too loose about UTF8 code points