Re: Index usage for elem-contained-by-const-range clauses

From: Robert Haas <robertmhaas(at)gmail(dot)com>
To: Pritam Baral <pritam(at)pritambaral(dot)com>
Cc: "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Index usage for elem-contained-by-const-range clauses
Date: 2017-02-26 13:46:26
Message-ID: CA+TgmoYTh=7DEu1umHZpgacOJjxRt0rkci7q-EaGqwyCrfm31g@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Thu, Feb 23, 2017 at 4:47 AM, Pritam Baral <pritam(at)pritambaral(dot)com> wrote:
> The topic has been previously discussed[0] on the -performance mailing list,
> about four years ago.
>
> In that thread, Tom suggested[0] the planner could be made to "expand
> "intcol <@
> 'x,y'::int4range" into "intcol between x and y", using something similar
> to the
> index LIKE optimization (ie, the "special operator" stuff in indxpath.c)".
>
> This patch tries to do exactly that.

Please add your patch to https://commitfest.postgresql.org/ so it
doesn't get overlooked.

--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Robert Haas 2017-02-26 14:00:32 Re: Performance degradation in TPC-H Q18
Previous Message Robert Haas 2017-02-26 13:39:52 Re: Enabling parallelism for queries coming from SQL or other PL functions