Received: from localhost.localdomain (postgresql.org [64.49.215.8]) by localhost (Postfix) with ESMTP id 501D1475D3D for ; Fri, 31 May 2002 04:18:23 -0400 (EDT) Received: from matrix.gatewaynet.com (unknown [217.19.69.50]) by postgresql.org (Postfix) with ESMTP id 1FCF5475D28 for ; Fri, 31 May 2002 04:18:16 -0400 (EDT) Received: from localhost (achill@localhost) by matrix.gatewaynet.com (8.11.6/8.11.6) with ESMTP id g4V8I0x26737 for ; Fri, 31 May 2002 11:18:00 +0300 Date: Fri, 31 May 2002 11:18:00 +0300 (EEST) From: Achilleus Mantzios To: pgsql-sql@postgresql.org Subject: contrib/intarray In-Reply-To: <011501c2037f$ad4b5340$9865fea9@Allan> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Archive-Number: 200205/325 X-Sequence-Number: 7960 Hi i found a rather strange behaviour in intarray. When i dont use indices or use the intbig version it works as expected. When i use gist__intbig_ops index, i returns something like "contained". To illustrate: (it is on the test__int table provided in the package). treetest=# DROP INDEX text_idx; DROP treetest=# select * from test__int where a= '{1}'; a --- (0 rows) treetest=# CREATE INDEX text_idx on test__int using gist ( a gist__intbig_ops ); CREATE treetest=# select * from test__int where a= '{1}'; a --- (0 rows) treetest=# DROP INDEX text_idx; DROP treetest=# CREATE INDEX text_idx on test__int using gist ( a gist__int_ops ); CREATE treetest=# select * from test__int where a= '{1}' limit 5; a ----------------- {11,56,1} {34,1,39,16} {41,1,87,40,60} {41,64,10,1} {60,88,95,1} (5 rows) treetest=# When the gist__int_ops index is created the result is different -- Achilleus Mantzios S/W Engineer IT dept Dynacom Tankers Mngmt tel: +30-10-8981112 fax: +30-10-8981877 email: achill@matrix.gatewaynet.com mantzios@softlab.ece.ntua.gr