Skip site navigation (1) Skip section navigation (2)

Re: BUG #3701: Don't work intarray GIN indexes

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: "girla" <girla(at)online(dot)ua>
Cc: pgsql-bugs(at)postgresql(dot)org
Subject: Re: BUG #3701: Don't work intarray GIN indexes
Date: 2007-10-26 19:42:19
Message-ID: (view raw, whole thread or download thread mbox)
Lists: pgsql-bugs
"girla" <girla(at)online(dot)ua> 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[] | 
    "text_idx" gin (a gin__int_ops)

contrib_regression=# SELECT count(*) from test__int WHERE a && '{23,50}';
(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)


(This is using the database set up by contrib/intarray's regression

So if you want help you're going to need to provide much more detail,
like say your *whole* test case.

			regards, tom lane

In response to

pgsql-bugs by date

Next:From: Herve BoulouisDate: 2007-10-28 10:22:52
Subject: Re: BUG #3362: xlog corruption just after initdb on irix
Previous:From: Chris BrowneDate: 2007-10-26 18:44:22
Subject: Re: The PostgreSQL Data directory Must be on an NTFS formatted Volume

Privacy Policy | About PostgreSQL
Copyright © 1996-2017 The PostgreSQL Global Development Group