| From: | "Andrey M(dot) Borodin" <x4mmm(at)yandex-team(dot)ru> |
|---|---|
| To: | Tomas Vondra <tomas(dot)vondra(at)enterprisedb(dot)com> |
| Cc: | "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: allow sorted builds for btree_gist |
| Date: | 2024-05-18 06:51:00 |
| Message-ID: | 8096891A-1DB4-4E30-89AF-0534D8E2BB01@yandex-team.ru |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
> On 18 May 2024, at 00:41, Tomas Vondra <tomas(dot)vondra(at)enterprisedb(dot)com> wrote:
>
> if the opclass supports sorted
> builds, because then we could parallelize the sort.
Hi Tomas!
Yup, I'd also be glad to see this feature. PostGIS folks are using their geometry (sortsupport was developed for this) with object id (this disables sort build).
It was committed once [0], but then reverted, vardata opclasses were implemented wrong. Now it's on CF[1], Bernd is actively responding in the thread, but currently patch lacks tests.
Thanks for raising this!
Best regards, Andrey Borodin.
[0] https://git.postgresql.org/gitweb/?p=postgresql.git;a=commit;h=9f984ba6d23dc
[1] https://commitfest.postgresql.org/48/3686/
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Jingxian Li | 2024-05-18 09:10:38 | Re: [PATCH] LockAcquireExtended improvement |
| Previous Message | Will Mortensen | 2024-05-18 06:38:35 | Re: [PATCH] LockAcquireExtended improvement |