Re: IN not handled very well? - Mailing list pgsql-performance

From Jim Nasby
Subject Re: IN not handled very well?
Date
Msg-id 03B144F0-FC55-41C0-B865-5DBF8816DB76@nasby.net
Whole thread Raw
In response to Re: IN not handled very well?  (Ben <bench@silentmedia.com>)
List pgsql-performance
On Sep 24, 2006, at 2:12 PM, Ben wrote:
> Ah, so I do. Thanks, that helps an awful lot.
>
> But the plan is still twice as expensive as when I put in the
> static values. Is it just unreasonable to expect the planner to see
> that there aren't many rows in the subselect, so to use the bitmap
> scans after all?

Based on your initial post, it probably should know that it's only
getting 15 rows (since it did in your initial plan), so it's unclear
why it's not choosing the bitmap scan.

Can you post the results of EXPLAIN ANALYZE?
--
Jim Nasby                                            jim@nasby.net
EnterpriseDB      http://enterprisedb.com      512.569.9461 (cell)



pgsql-performance by date:

Previous
From: Jim Nasby
Date:
Subject: Re: Update on high concurrency OLTP application and Postgres
Next
From: Jim Nasby
Date:
Subject: Re: Decreasing BLKSZ