On Tue, Jun 11, 2013 at 08:42:26PM -0400, Andrew Dunstan wrote: > If we work by analogy to Postgres' own handling of Unicode escapes, > we'll raise an error on any Unicode escape beyond ASCII (not on input > for legacy reasons, but on trying to process such datums). I gather that > would meet your objection.
No objection here; that approach is free from the problem that caught my attention in the other proposal. -- Noah Misch EnterpriseDB http://www.enterprisedb.com -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
