Re: Unicode normalization test broken output
Peter Eisentraut <peter.eisentraut@2ndquadrant.com>
From: Peter Eisentraut <peter.eisentraut@2ndquadrant.com>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: pgsql-hackers <pgsql-hackers@postgresql.org>
Date: 2019-12-10T12:18:31Z
Lists: pgsql-hackers
Attachments
- v2-0001-Fix-output-of-Unicode-normalization-test.patch (text/plain) patch v2-0001
On 2019-12-09 23:22, Tom Lane wrote: > Peter Eisentraut <peter.eisentraut@2ndquadrant.com> writes: >> There appear to be several off-by-more-than-one errors in norm_test.c >> print_wchar_str(). Attached is a patch to fix this (and make the output >> a bit prettier). Result afterwards: > > I concur that this looks broken and your patch improves it. > But I'm not very happy about the remaining assumption that > we don't have to worry about characters above U+FFFF. I'd > rather see it allocate 11 bytes per allowed pg_wchar, and > manage the string contents with something like > > p += sprintf(p, "U+%04X ", *s); Good point. Fixed in attached patch. -- Peter Eisentraut http://www.2ndQuadrant.com/ PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
Commits
-
Fix output of Unicode normalization test
- b802412106e8 13.0 landed