From: Peter Eisentraut <peter.eisentraut@2ndquadrant.com>
To: Daniel Verite <daniel@manitou-mail.org>
Cc: Andreas Karlsson <andreas@proxel.se>
Cc: pgsql-hackers <pgsql-hackers@postgresql.org>
Subject: Re: Unicode normalization SQL functions
Date: Tue, 24 Mar 2020 10:20:54 +0100
Message-ID: <620b155b-a89c-d8e0-3cbb-315c3ca538f4@2ndquadrant.com> (raw)
In-Reply-To: <6d55838c-9353-486f-a508-77ee07d59667@manitou-mail.org>
References: <6d55838c-9353-486f-a508-77ee07d59667@manitou-mail.org>
On 2020-03-23 17:26, Daniel Verite wrote:
> Peter Eisentraut wrote:
>
>> What is that status of this patch set? I think we have nailed down the
>> behavior, but there were some concerns about certain performance
>> characteristics. Do people feel that those are required to be addressed
>> in this cycle?
>
> Not finding any other issue with v3 or objections in the thread,
> I've set the status to Ready For Committer in the CF.
I have committed the 0001 patch.
Now I have some concerns about the size of the new table in
unicode_normprops_table.h, and the resulting binary size. At the very
least, we should probably make that #ifndef FRONTEND or something like
that so libpq isn't bloated by it unnecessarily. Perhaps there is a
better format for that table? Any ideas?
--
Peter Eisentraut http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-hackers@postgresql.org
Cc: peter.eisentraut@2ndquadrant.com, daniel@manitou-mail.org, andreas@proxel.se
Subject: Re: Unicode normalization SQL functions
In-Reply-To: <620b155b-a89c-d8e0-3cbb-315c3ca538f4@2ndquadrant.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox