Skip site navigation (1) Skip section navigation (2)

Re: TODO Item: IN(long list ...)

From: Josh Berkus <josh(at)agliodbs(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Alvaro Herrera <alvherre(at)commandprompt(dot)com>, pgsql-hackers(at)postgresql(dot)org
Subject: Re: TODO Item: IN(long list ...)
Date: 2006-10-31 22:34:21
Message-ID: 200610311434.22296.josh@agliodbs.com (view raw or flat)
Thread:
Lists: pgsql-hackers
Tom,

> I think it's pretty much done.  Try WHERE foo IN (VALUES (1),(2),...)
> if you have so many values that a non-nestloop join seems indicated.

Hmmm.  Was there a reason not to automate this?   Thread link is fine if 
you can remember the subject line ... I can't find it on archives.

> The plain non-VALUES list form is also significantly faster than it
> was, but I think it will only result in a bitmap indexscan plan type.

Yeah, even bitmapscans break down at 1000 values ...

-- 
--Josh

Josh Berkus
PostgreSQL @ Sun
San Francisco

In response to

pgsql-hackers by date

Next:From: Henry B. HotzDate: 2006-11-01 00:14:17
Subject: Design Considerations for New Authentication Methods
Previous:From: Tom LaneDate: 2006-10-31 21:44:44
Subject: Re: zic data updates

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group