"girla" <[EMAIL PROTECTED]> writes:
> 8.3beta1 never used intarray GIN indexes.
Works for me:
contrib_regression=# \d test__int
Table "public.test__int"
Column | Type | Modifiers
--------+-----------+-----------
a | integer[] |
Indexes:
"text_idx" gin (a gin__int_ops)
contrib_regression=# SELECT count(*) from test__int WHERE a && '{23,50}';
count
-------
403
(1 row)
contrib_regression=# explain SELECT count(*) from test__int WHERE a &&
'{23,50}';
QUERY PLAN
-----------------------------------------------------------------------------
Aggregate (cost=25.18..25.19 rows=1 width=0)
-> Bitmap Heap Scan on test__int (cost=4.31..25.16 rows=7 width=0)
Recheck Cond: (a && '{23,50}'::integer[])
-> Bitmap Index Scan on text_idx (cost=0.00..4.31 rows=7 width=0)
Index Cond: (a && '{23,50}'::integer[])
(5 rows)
contrib_regression=#
(This is using the database set up by contrib/intarray's regression
test.)
So if you want help you're going to need to provide much more detail,
like say your *whole* test case.
regards, tom lane
---------------------------(end of broadcast)---------------------------
TIP 6: explain analyze is your friend
