From: | Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com> |
---|---|
To: | Daniel Verite <daniel(at)manitou-mail(dot)org> |
Cc: | Andreas Karlsson <andreas(at)proxel(dot)se>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: Unicode normalization SQL functions |
Date: | 2020-03-24 09:20:54 |
Message-ID: | 620b155b-a89c-d8e0-3cbb-315c3ca538f4@2ndquadrant.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
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
From | Date | Subject | |
---|---|---|---|
Next Message | Kyotaro Horiguchi | 2020-03-24 09:24:13 | Re: Remove page-read callback from XLogReaderState. |
Previous Message | Amit Kapila | 2020-03-24 09:18:51 | Re: error context for vacuum to include block number |