Re: [GENERAL] Bad plan using join on VALUES (and now on temp table too)

2007-04-10 Thread Listmail
Well, the planner probably guessed that in your case it's faster to scan the table than to use the index (indexes are not free). Did it choose wrong? Yes, see the other query in my post... id IN ( 60 values ) => 0.582 ms (bitmap scan on the index : perfect) join with V

Re: [GENERAL] Bad plan using join on VALUES

2007-04-10 Thread Martijn van Oosterhout
On Tue, Apr 10, 2007 at 10:57:43AM +0200, Listmail wrote: > > Table definition and problem query is below. I'm surprised... Well, the planner probably guessed that in your case it's faster to scan the table than to use the index (indexes are not free). Did it choose wrong? If you disable th