| From: | David Geier <geidav(dot)pg(at)gmail(dot)com> |
|---|---|
| To: | John Naylor <johncnaylorls(at)gmail(dot)com>, Heikki Linnakangas <hlinnaka(at)iki(dot)fi> |
| Cc: | Matthias van de Meent <boekewurm+postgres(at)gmail(dot)com>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Reduce build times of pg_trgm GIN indexes |
| Date: | 2026-04-13 15:05:30 |
| Message-ID: | 07c79a83-94aa-4d54-95b9-cba2a29565c1@gmail.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 08.04.2026 04:15, John Naylor wrote:
> On Tue, Apr 7, 2026 at 6:27 PM Heikki Linnakangas <hlinnaka(at)iki(dot)fi> wrote:
>> But the comments on the pg_cmp functions say:
>>
>>> * NB: If the comparator function is inlined, some compilers may produce
>>> * worse code with these helper functions than with code with the
>>> * following form:
>>> *
>>> * if (a < b)
>>> * return -1;
>>> * if (a > b)
>>> * return 1;
>>> * return 0;
>>> *
>>
>> So, uh, is that really a universal improvement? Is that comment about
>> producing worse code outdated?
Well spotted. Thanks!
>
> No, it's quite recent:
>
> https://www.postgresql.org/message-id/20240212230423.GA3519%40nathanxps13
In my original benchmarks it was faster. I'll rebase the remaining
commits and do some more analysis.
--
David Geier
| From | Date | Subject | |
|---|---|---|---|
| Next Message | David Geier | 2026-04-13 15:06:40 | Re: Reduce build times of pg_trgm GIN indexes |
| Previous Message | David Geier | 2026-04-13 15:03:11 | Re: Reduce build times of pg_trgm GIN indexes |