Re: Feature - Index support on an lquery field (from the ltree module)

From: Heikki Linnakangas <hlinnaka(at)iki(dot)fi>
To: David Belle <david(dot)belle(at)codewhite(dot)com(dot)au>, pgsql-hackers(at)postgresql(dot)org
Subject: Re: Feature - Index support on an lquery field (from the ltree module)
Date: 2015-07-28 05:00:31
Message-ID: 55B70C6F.6090506@iki.fi
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On 07/28/2015 06:40 AM, David Belle wrote:
> I have a requirement for a project that I am working on and was
> hoping to gain some discussion on the idea of implementing an index
> type for lquery fields (see ltree’s
> http://www.postgresql.org/docs/9.4/static/ltree.html
> <http://www.postgresql.org/docs/9.4/static/ltree.html>)
>
> Currently ltree fields can have GIST/GIN indexes, but you cannot
> create a index for lquery or ltxtquery. In my scope, an index for
> lquery would be enough, although if it wasn’t too difficult it for to
> be expanded for ltxtquery fields, then this could also be
> implemented.

Hmm. My first thought is to extract labels from the query which are
required for any matches, and put those in the GIN index. When querying,
find all lqueries that have at least one label in common with the search
key.

- Heikki

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Amit Langote 2015-07-28 05:48:38 Re: [DESIGN] ParallelAppend
Previous Message Amit Kapila 2015-07-28 04:24:06 Re: [DESIGN] ParallelAppend