BUG #3701: Don't work intarray GIN indexes

From: "girla" <girla(at)online(dot)ua>
To: pgsql-bugs(at)postgresql(dot)org
Subject: BUG #3701: Don't work intarray GIN indexes
Date: 2007-10-26 18:27:22
Message-ID: 200710261827.l9QIRMAK008516@wwwmaster.postgresql.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs


The following bug has been logged online:

Bug reference: 3701
Logged by: girla
Email address: girla(at)online(dot)ua
PostgreSQL version: 8.3beta1
Operating system: Windows XP Proffesional SP2
Description: Don't work intarray GIN indexes
Details:

8.3beta1 never used intarray GIN indexes.

The same test case:

EXPLAIN
SELECT *
FROM intarr
WHERE (arr && ARRAY[132,20,78,45,457]);

on 8.2:
--------------------
"Bitmap Heap Scan on intarr (cost=4.33..37.45 rows=10 width=64)"
" Recheck Cond: (arr && '{132,20,78,45,457}'::integer[])"
" -> Bitmap Index Scan on i_arr_gin (cost=0.00..4.33 rows=10 width=0)"
" Index Cond: (arr && '{132,20,78,45,457}'::integer[])"

and on 8.3beta1:
---------------------
"Seq Scan on intarr (cost=0.00..238.00 rows=10 width=58)"
" Filter: (arr && '{132,20,78,45,457}'::integer[])"

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Chris Browne 2007-10-26 18:44:22 Re: The PostgreSQL Data directory Must be on an NTFS formatted Volume
Previous Message Tom Lane 2007-10-26 18:12:55 Re: Possible planner bug/regression introduced in 8.2.5