postgresql/contrib/btree_gist/expected/int2.out
Heikki Linnakangas d92b1cdbab Revert "Add sortsupport for gist_btree opclasses, for faster index builds."
This reverts commit 9f984ba6d2.

It was making the buildfarm unhappy, apparently setting client_min_messages
in a regression test produces different output if log_statement='all'.
Another issue is that I now suspect the bit sortsupport function was in
fact not correct to call byteacmp(). Revert to investigate both of those
issues.
2021-04-07 14:33:21 +03:00

92 lines
1.5 KiB
Plaintext

-- int2 check
CREATE TABLE int2tmp (a int2);
\copy int2tmp from 'data/int2.data'
SET enable_seqscan=on;
SELECT count(*) FROM int2tmp WHERE a < 237;
count
-------
297
(1 row)
SELECT count(*) FROM int2tmp WHERE a <= 237;
count
-------
298
(1 row)
SELECT count(*) FROM int2tmp WHERE a = 237;
count
-------
1
(1 row)
SELECT count(*) FROM int2tmp WHERE a >= 237;
count
-------
249
(1 row)
SELECT count(*) FROM int2tmp WHERE a > 237;
count
-------
248
(1 row)
SELECT a, a <-> '237' FROM int2tmp ORDER BY a <-> '237' LIMIT 3;
a | ?column?
-----+----------
237 | 0
232 | 5
228 | 9
(3 rows)
CREATE INDEX int2idx ON int2tmp USING gist ( a );
SET enable_seqscan=off;
SELECT count(*) FROM int2tmp WHERE a < 237::int2;
count
-------
297
(1 row)
SELECT count(*) FROM int2tmp WHERE a <= 237::int2;
count
-------
298
(1 row)
SELECT count(*) FROM int2tmp WHERE a = 237::int2;
count
-------
1
(1 row)
SELECT count(*) FROM int2tmp WHERE a >= 237::int2;
count
-------
249
(1 row)
SELECT count(*) FROM int2tmp WHERE a > 237::int2;
count
-------
248
(1 row)
EXPLAIN (COSTS OFF)
SELECT a, a <-> '237' FROM int2tmp ORDER BY a <-> '237' LIMIT 3;
QUERY PLAN
------------------------------------------------
Limit
-> Index Only Scan using int2idx on int2tmp
Order By: (a <-> '237'::smallint)
(3 rows)
SELECT a, a <-> '237' FROM int2tmp ORDER BY a <-> '237' LIMIT 3;
a | ?column?
-----+----------
237 | 0
232 | 5
228 | 9
(3 rows)