Skip site navigation (1)
Skip section navigation (2)
Peripheral Links
Header And Logo
|
Site Navigation
Re: slow IN() clause for many cases
- From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
- To: andrew(at)supernews(dot)com
- Cc: pgsql-hackers(at)postgresql(dot)org
- Subject: Re: slow IN() clause for many cases
- Date: Fri, 14 Oct 2005 19:09:17 -0400
- Message-id: <8063(dot)1129331357(at)sss(dot)pgh(dot)pa(dot)us>
I wrote: > I'm thinking that IN should be > converted to a ScalarArrayOpExpr, ie > x = ANY (ARRAY[val1,val2,val3,val4,...]) Actually, there is one little thing in the way of doing this: it'll fail if any of the IN-list elements are NULL, because we have not got support for arrays with null elements. So we'd have to fix that first. regards, tom lane
- Follow-Ups:
- Re: slow IN() clause for many cases
- From: Simon Riggs
- Re: slow IN() clause for many cases
- From: mark
- Re: slow IN() clause for many cases
- From: David Fetter
- Re: slow IN() clause for many cases
- References:
- Re: slower merge join on sorted data chosen over
- From: Simon Riggs
- Re: slow IN() clause for many cases
- From: Ilia Kantor
- Re: slow IN() clause for many cases
- From: Andrew - Supernews
- Re: slow IN() clause for many cases
- From: Tom Lane
- Re: slow IN() clause for many cases
- From: Andrew - Supernews
- Re: slow IN() clause for many cases
- From: Andrew - Supernews
- Re: slow IN() clause for many cases
- From: Tom Lane
- Re: slower merge join on sorted data chosen over
- Prev by Date: Re: slow IN() clause for many cases
- Next by Date: Re: slow IN() clause for many cases
- Previous by thread: Re: slow IN() clause for many cases
- Next by thread: Re: slow IN() clause for many cases
- Indexes: