Horton

Re: speed up unicode normalization quick check

John Naylor <john.naylor@enterprisedb.com>

View thread View on postgr.es
From: John Naylor <john.naylor@enterprisedb.com>
To: Michael Paquier <michael@paquier.xyz>
Cc: Mark Dilger <mark.dilger@enterprisedb.com>, PostgreSQL Hackers <pgsql-hackers@lists.postgresql.org>
Date: 2020-10-08T22:22:39Z
Lists: pgsql-hackers 
On Thu, Oct 8, 2020 at 8:29 AM Michael Paquier <michael@paquier.xyz> wrote:

> On Thu, Oct 08, 2020 at 04:52:18AM -0400, John Naylor wrote:
> > Looks fine overall, but one minor nit: I'm curious why you made a
> separate
> > section in the pgindent exclusions. The style in that file seems to be
> one
> > comment per category.
>
> Both parts indeed use PerfectHash.pm, but are generated by different
> scripts so that looked better as separate items.


Okay, thanks.

--
John Naylor
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company

Commits

  1. Review format of code generated by PerfectHash.pm

  2. Fix compilation warning in unicode_norm.c

  3. Use perfect hash for NFC and NFKC Unicode Normalization quick check

  4. Improve set of candidate multipliers for perfect hash function generation

  5. Further improve pgindent's list of file exclusions.