mirror of
https://github.com/postgres/postgres.git
synced 2025-10-29 22:49:41 +03:00
d92b1cdbab
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.
37 lines
982 B
SQL
37 lines
982 B
SQL
-- varbit check
|
|
|
|
CREATE TABLE varbittmp (a varbit);
|
|
|
|
\copy varbittmp from 'data/varbit.data'
|
|
|
|
SET enable_seqscan=on;
|
|
|
|
SELECT count(*) FROM varbittmp WHERE a < '1110100111010';
|
|
|
|
SELECT count(*) FROM varbittmp WHERE a <= '1110100111010';
|
|
|
|
SELECT count(*) FROM varbittmp WHERE a = '1110100111010';
|
|
|
|
SELECT count(*) FROM varbittmp WHERE a >= '1110100111010';
|
|
|
|
SELECT count(*) FROM varbittmp WHERE a > '1110100111010';
|
|
|
|
CREATE INDEX varbitidx ON varbittmp USING GIST ( a );
|
|
|
|
SET enable_seqscan=off;
|
|
|
|
SELECT count(*) FROM varbittmp WHERE a < '1110100111010'::varbit;
|
|
|
|
SELECT count(*) FROM varbittmp WHERE a <= '1110100111010'::varbit;
|
|
|
|
SELECT count(*) FROM varbittmp WHERE a = '1110100111010'::varbit;
|
|
|
|
SELECT count(*) FROM varbittmp WHERE a >= '1110100111010'::varbit;
|
|
|
|
SELECT count(*) FROM varbittmp WHERE a > '1110100111010'::varbit;
|
|
|
|
-- Test index-only scans
|
|
SET enable_bitmapscan=off;
|
|
EXPLAIN (COSTS OFF)
|
|
SELECT a FROM bittmp WHERE a BETWEEN '1000000' and '1000001';
|