Re: [PATCH] Add sortsupport for range types and btree_gist

From: Bernd Helmle <mailings(at)oopsware(dot)de>
To: "Andrey M(dot) Borodin" <x4mmm(at)yandex-team(dot)ru>
Cc: jian he <jian(dot)universality(at)gmail(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>
Subject: Re: [PATCH] Add sortsupport for range types and btree_gist
Date: 2024-11-11 16:41:25
Message-ID: 61128550659807032dd29c8c8a71674c818cbbb6.camel@oopsware.de
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Am Samstag, dem 26.10.2024 um 11:40 +0300 schrieb Andrey M. Borodin:
> First patch:
> 0. We have PG_FREE_IF_COPY(), does it suits your needs?
> 1. Tests do not check what actual build method is used. You can add
> INJECTION_POINT("gist-sort-build") and expect a notice there or
> something like that.
> 2. "Per default" -> "By default", "indexe" -> "index", "index
> quality" -> NULL (in 14 quality was bad, since 15 same "quality")
>

Updated and rebased patches attached. I used the injection point name
"btree-gist-sorted-build".

> Second patch:
> 0. PG_FREE_IF_COPY in range_gist_cmp? :)
> 1. Some test of this new functionality?

I added the same injection point here, too, since the functionalitly is
already employed in btree_gist regression tests "partition" and
"without_overlap".

Except the suggestions for PG_FREE_IF_COPY(), this updated patch set
reflects all the comments from Andrey above.

Playing with these suggested changes also revealed some bugs (i
confused some of the comparator functions for macaddr*), so thanks
again for the review!

Thanks,
Bernd

Attachment Content-Type Size
v7.3-Add-GIST-sortsupport-btree-gist.patch text/x-patch 313.3 KB
v7.3-Add-GIST-sortsupport-rangetypes.patch text/x-patch 4.2 KB

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Fujii Masao 2024-11-11 16:49:34 Re: Add reject_limit option to file_fdw
Previous Message Jacob Champion 2024-11-11 16:34:48 Offsets of `struct Port` are no longer constant