Paul Jungwirth writes:
> On 7/6/24 05:04, Andrey M. Borodin wrote:>> On 5 Jul 2024, at 23:46, Paul
> Jungwirth
> wrote:
>>> this commit adds support for all combinations of int2/int4/int8 for all
>>> five btree operators (=/>).
Perhaps I'm missing something, but how can this possibly work wit
On 7/6/24 05:04, Andrey M. Borodin wrote:>> On 5 Jul 2024, at 23:46, Paul Jungwirth
wrote:
this commit adds support for all combinations of int2/int4/int8 for all five btree
operators (=/>).
Looks like a nice feature to have.
Would it make sense to do something similar to float8? Or, perhaps
> On 5 Jul 2024, at 23:46, Paul Jungwirth wrote:
>
> this commit adds support for all combinations of int2/int4/int8 for all five
> btree operators (=/>).
Looks like a nice feature to have.
Would it make sense to do something similar to float8? Or, perhaps, some other
types from btree_gist?
Hi Hackers,
I noticed that this query wasn't using my GiST index:
postgres=# create extension btree_gist;
CREATE EXTENSION
postgres=# create table t (id bigint, valid_at daterange, exclude using gist (id with =, valid_at
with &&));
CREATE TABLE
postgres=# explain select * from t where id = 5;
