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-10-28 17:44:10 |
Message-ID: | 90e9c41bbe7e21c5fc8815f0bb96dd97ed7fda39.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?
PG_FREE_IF_COPY() requires FunctionCallInfo (the macro uses
PG_GETARG_POINTER() to reference the pointer value to compare), which
is not usable in the context we need it.
> 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.
Hmm good idea, i give it a try.
> 2. "Per default" -> "By default", "indexe" -> "index", "index
> quality" -> NULL (in 14 quality was bad, since 15 same "quality")
>
> Second patch:
> 0. PG_FREE_IF_COPY in range_gist_cmp? :)
See above.
> 1. Some test of this new functionality?
Right, but i am unsure where this belongs to. Perhaps to
src/test/regress/sql/rangetypes.sql ? We can extend the gist tests
there.
From | Date | Subject | |
---|---|---|---|
Next Message | Masahiko Sawada | 2024-10-28 17:50:37 | Re: New "raw" COPY format |
Previous Message | Marcos Pegoraro | 2024-10-28 17:29:44 | Re: Should we support casting between ARRAYs and JSON(B)? |