Hi,
I'm not really sure which part you condides a bug? We simply don't
translate between IN() and OR-ed conditions, and there may be some
costing differences. So we may generate different plans, and the switch
between index scan and bitmap index scan may happen at different points.
On 11/20/21 17:52, PG Bug reporting form wrote:
>
> EXPLAIN SELECT * FROM t WHERE a IN (142,147,153,199);
> -- Bitmap Heap Scan on t (cost=3739.74..50987.74 rows=200000 width=8)
> |
> -- Recheck Cond: (a = ANY ('{142,147,153,199}'::integer[]))
> |
> -- -> Bitmap Index Scan on t_i (cost=0.00..3689.74 rows=200000
> width=0)|
> -- Index Cond: (a = ANY ('{142,147,153,199}'::integer[]))
> |
This is rather strange, though. Why would this have estimate 200000? The
other query has estimate 4, so it can't be because of missing stats etc.
Or why would it fix after several minutes?
regards
--
Tomas Vondra
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
