From: | Michał Kłeczek <michal(at)kleczek(dot)org> |
---|---|
To: | Tomas Vondra <tomas(dot)vondra(at)enterprisedb(dot)com> |
Cc: | PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: allow sorted builds for btree_gist |
Date: | 2024-05-18 18:42:41 |
Message-ID: | 1CF6E107-AFC9-4D28-BA2E-CE29B7C40E3C@kleczek.org |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
> On 17 May 2024, at 21:41, Tomas Vondra <tomas(dot)vondra(at)enterprisedb(dot)com> wrote:
>
> Hi,
>
> I've been looking at GiST to see if there could be a good way to do
> parallel builds - and there might be, if the opclass supports sorted
> builds, because then we could parallelize the sort.
>
> But then I noticed we support this mode only for point_ops, because
> that's the only opclass with sortsupport procedure. Which mostly makes
> sense, because types like geometries, polygons, ... do not have a well
> defined order.
>
> Still, we have btree_gist, and I don't think there's much reason to not
> support sorted builds for those opclasses, where the gist opclass is
> defined on top of btree ordering semantics.
>
I wonder if it was possible to add sort support to pg_trgm. Speeding up index build for multicolumn indexes supporting text search would be great.
—
Michal
From | Date | Subject | |
---|---|---|---|
Next Message | Andrey M. Borodin | 2024-05-18 18:52:11 | Sort functions with specialized comparators |
Previous Message | Tom Lane | 2024-05-18 16:58:03 | Re: Speed up clean meson builds by ~25% |