Re: [PATCH] ltree hash functions - Mailing list pgsql-hackers

From jian he
Subject Re: [PATCH] ltree hash functions
Date
Msg-id CACJufxGd4_qSqU3-j9TFOS7JD0Jx+fSFNdVBnEeprP35ppFscQ@mail.gmail.com
Whole thread Raw
In response to Re: [PATCH] ltree hash functions  (Tommy Pavlicek <tommypav122@gmail.com>)
Responses Re: [PATCH] ltree hash functions
List pgsql-hackers
On Wed, Nov 29, 2023 at 6:09 AM Tommy Pavlicek <tommypav122@gmail.com> wrote:
>
> On Thu, Jul 6, 2023 at 2:18 AM Daniel Gustafsson <daniel@yesql.se> wrote:
> >
> > > On 19 Jun 2023, at 11:18, Tommy Pavlicek <tommypav122@gmail.com> wrote:
> >
> > > Tommy, are you interested in extending ALTER OPERATOR to allow this,
> > > which would also allow fixing the ltree operator?
> > >
> > > Yes, I can do that. I took a look over the code and email thread and it seems like it should be relatively
straightforward. I'll put a patch together for that and then update this patch to alter the operator. 
> >
> > Did you have a chance to look at this for an updated patch for this commitfest?
>
> I finally had a chance to look at this and I've updated the patch to
> alter the = operator to enable hash joins.
>
> This is ready to be looked at now.
>
> Is there anything I need to do to move this forward?
>

you only change Makefile, you also need to change contrib/ltree/meson.build?

+drop index tstidx;
+create index tstidx on ltreetest using hash (t);
+set enable_seqscan=off;
+
+SELECT * FROM ltreetest WHERE t =  '12.3' order by t asc;

Do you need to use EXPLAIN to demo the index usage?



pgsql-hackers by date:

Previous
From: Melanie Plageman
Date:
Subject: Re: Streaming I/O, vectored I/O (WIP)
Next
From: Andrew Dunstan
Date:
Subject: Re: remaining sql/json patches