On 9/23/09, Peter Eisentraut <pete...@gmx.net> wrote: > On Wed, 2009-09-09 at 18:26 +0300, Marko Kreen wrote: > > Unicode escapes for extended strings. > > Committed.
Thank you for handling the patch. I looked at your code for U& and saw that you allow standalone second half of the surrogate pair there, although you error out on first half. Was that deliberate? Standalone surrogate halfs cause headaches for anything that wants to handle data in UTF16. The area 0xD800-0xDFFF is explicitly reserved for UTF16 encoding and does not contain any valid Unicode codepoints. Perhaps pg_verifymbstr() should be made to check for such values, because even if we fix the escaping code, such data can still be inserted via plain utf8 or \x escapes? -- marko -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
