Re: Performance improvement for queries with IN clause - Mailing list pgsql-hackers

From Amit Kapila
Subject Re: Performance improvement for queries with IN clause
Date
Msg-id CAA4eK1LBUXWzmO84XPM5HXT1XT=xYpRAPHDvmnXNiy4jdt3EoQ@mail.gmail.com
Whole thread Raw
In response to Re: Performance improvement for queries with IN clause  (Andreas Karlsson <andreas@proxel.se>)
List pgsql-hackers
On Sat, Nov 9, 2019 at 5:22 PM Andreas Karlsson <andreas@proxel.se> wrote:
>
> On 11/8/19 2:52 PM, Rafia Sabih wrote:
> > Now, my question is shouldn't we always use this list in sorted order,
> > in other words can there be scenarios where such a sorting will not
> > help? I am talking about only the cases where the list consists of all
> > constants and could fit in memory. Basically, when we are
> > transforming the in expression and found that it consists of all
> > constants, then sort it as well, codewise at transfromAExprIn, of course
> > there might be better ways to accomplish this.
> >
> > So, your thoughts, opinions, suggestions are more than welcome.
>
> If it is worth sorting them should depend on the index, e.g. for hash
> indexes sorting would just be a waste of time.
>

I think we also need to be careful that this might lead to regression
for cases where the list is already sorted.

-- 
With Regards,
Amit Kapila.
EnterpriseDB: http://www.enterprisedb.com



pgsql-hackers by date:

Previous
From: Eugen Konkov
Date:
Subject: Re: Does 'instead of delete' trigger support modification of OLD
Next
From: Andrew Dunstan
Date:
Subject: Re: TestLib::command_fails_like enhancement