contrib/intarray

From: Achilleus Mantzios <achill(at)matrix(dot)gatewaynet(dot)com>
To: pgsql-sql(at)postgresql(dot)org
Subject: contrib/intarray
Date: 2002-05-31 08:18:00
Message-ID: Pine.LNX.4.44.0205311112210.26712-100000@matrix.gatewaynet.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-sql


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(at)matrix(dot)gatewaynet(dot)com
mantzios(at)softlab(dot)ece(dot)ntua(dot)gr

In response to

Responses

Browse pgsql-sql by date

  From Date Subject
Next Message Henshall, Stuart - WCP 2002-05-31 08:50:23 Re: question on JOIN and WHERE clause
Previous Message Achilleus Mantzios 2002-05-31 06:36:53 Re: Math Huh?