Re: speed up unicode normalization quick check
John Naylor <john.naylor@2ndquadrant.com>
From: John Naylor <john.naylor@2ndquadrant.com>
To: Mark Dilger <mark.dilger@enterprisedb.com>
Cc: PostgreSQL Hackers <pgsql-hackers@lists.postgresql.org>
Date: 2020-09-18T16:41:02Z
Lists: pgsql-hackers
Attachments
- v4-0001-Tweak-the-set-of-candidate-multipliers-for-genera.patch (application/x-patch) patch v4-0001
- v4-0002-Use-perfect-hashing-for-NFC-Unicode-normalization.patch (application/x-patch) patch v4-0002
- v4-0003-Use-perfect-hashing-for-NKFC-Unicode-normalizatio.patch (application/x-patch) patch v4-0003
Attached is version 4, which excludes the output file from pgindent, to match recent commit 74d4608f5. Since it won't be indented again, I also tweaked the generator script to match pgindent for the typedef, since we don't want to lose what pgindent has fixed already. This last part isn't new to v4, but I thought I'd highlight it anyway. -- John Naylor https://www.2ndQuadrant.com/ PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
Commits
-
Review format of code generated by PerfectHash.pm
- 19ae53c92d5f 14.0 landed
-
Fix compilation warning in unicode_norm.c
- e578c17d8166 14.0 landed
-
Use perfect hash for NFC and NFKC Unicode Normalization quick check
- 80f8eb79e24d 14.0 landed
-
Improve set of candidate multipliers for perfect hash function generation
- 2a7316458164 14.0 landed
-
Further improve pgindent's list of file exclusions.
- 74d4608f506b 14.0 cited