postgresql/contrib/btree_gist/expected/varbit.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

77 lines
1.5 KiB
Plaintext

-- varbit check
CREATE TABLE varbittmp (a varbit);
\copy varbittmp from 'data/varbit.data'
SET enable_seqscan=on;
SELECT count(*) FROM varbittmp WHERE a < '1110100111010';
count
-------
549
(1 row)
SELECT count(*) FROM varbittmp WHERE a <= '1110100111010';
count
-------
550
(1 row)
SELECT count(*) FROM varbittmp WHERE a = '1110100111010';
count
-------
1
(1 row)
SELECT count(*) FROM varbittmp WHERE a >= '1110100111010';
count
-------
51
(1 row)
SELECT count(*) FROM varbittmp WHERE a > '1110100111010';
count
-------
50
(1 row)
CREATE INDEX varbitidx ON varbittmp USING GIST ( a );
SET enable_seqscan=off;
SELECT count(*) FROM varbittmp WHERE a < '1110100111010'::varbit;
count
-------
549
(1 row)
SELECT count(*) FROM varbittmp WHERE a <= '1110100111010'::varbit;
count
-------
550
(1 row)
SELECT count(*) FROM varbittmp WHERE a = '1110100111010'::varbit;
count
-------
1
(1 row)
SELECT count(*) FROM varbittmp WHERE a >= '1110100111010'::varbit;
count
-------
51
(1 row)
SELECT count(*) FROM varbittmp WHERE a > '1110100111010'::varbit;
count
-------
50
(1 row)
-- Test index-only scans
SET enable_bitmapscan=off;
EXPLAIN (COSTS OFF)
SELECT a FROM bittmp WHERE a BETWEEN '1000000' and '1000001';
QUERY PLAN
---------------------------------------------------------------------
Index Only Scan using bitidx on bittmp
Index Cond: ((a >= '1000000'::"bit") AND (a <= '1000001'::"bit"))
(2 rows)