pg.ddx.io pgsql-sql@postgresql.org mailing list archive
help / color / mirror / Atom feedcontrib/intarray
2+ messages / 2 participants
[nested] [flat]
* contrib/intarray
@ 2002-05-31 08:18 Achilleus Mantzios <achill@matrix.gatewaynet.com>
0 siblings, 1 reply; 2+ messages in thread
From: Achilleus Mantzios @ 2002-05-31 08:18 UTC (permalink / raw)
To: 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@matrix.gatewaynet.com
mantzios@softlab.ece.ntua.gr
^ permalink raw reply [nested|flat] 2+ messages in thread
* Re: contrib/intarray
@ 2002-05-31 11:10 Oleg Bartunov <oleg@sai.msu.su>
parent: Achilleus Mantzios <achill@matrix.gatewaynet.com>
0 siblings, 0 replies; 2+ messages in thread
From: Oleg Bartunov @ 2002-05-31 11:10 UTC (permalink / raw)
To: Achilleus Mantzios <achill@matrix.gatewaynet.com>; +Cc: pgsql-sql
There is probably a bug in gist__int_ops ( 'contained' ops used instead of '=')
We'll submit fix later
Oleg
On Fri, 31 May 2002, Achilleus Mantzios wrote:
>
> 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
>
>
Regards,
Oleg
_____________________________________________________________
Oleg Bartunov, sci.researcher, hostmaster of AstroNet,
Sternberg Astronomical Institute, Moscow University (Russia)
Internet: oleg@sai.msu.su, http://www.sai.msu.su/~megera/
phone: +007(095)939-16-83, +007(095)939-23-83
^ permalink raw reply [nested|flat] 2+ messages in thread
end of thread, other threads:[~2002-05-31 11:10 UTC | newest]
Thread overview: 2+ messages (download: mbox mbox.gz follow: Atom feed)
-- links below jump to the message on this page --
2002-05-31 08:18 contrib/intarray Achilleus Mantzios <achill@matrix.gatewaynet.com>
2002-05-31 11:10 ` Oleg Bartunov <oleg@sai.msu.su>
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox