mirror of
https://github.com/postgres/postgres.git
synced 2025-04-20 00:42:27 +03:00
d92b1cdbab
This reverts commit 9f984ba6d23dc6eecebf479ab1d3f2e550a4e9be. 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
1.1 KiB
SQL
37 lines
1.1 KiB
SQL
-- bit check
|
|
|
|
CREATE TABLE bittmp (a bit(33));
|
|
|
|
\copy bittmp from 'data/bit.data'
|
|
|
|
SET enable_seqscan=on;
|
|
|
|
SELECT count(*) FROM bittmp WHERE a < '011011000100010111011000110000100';
|
|
|
|
SELECT count(*) FROM bittmp WHERE a <= '011011000100010111011000110000100';
|
|
|
|
SELECT count(*) FROM bittmp WHERE a = '011011000100010111011000110000100';
|
|
|
|
SELECT count(*) FROM bittmp WHERE a >= '011011000100010111011000110000100';
|
|
|
|
SELECT count(*) FROM bittmp WHERE a > '011011000100010111011000110000100';
|
|
|
|
CREATE INDEX bitidx ON bittmp USING GIST ( a );
|
|
|
|
SET enable_seqscan=off;
|
|
|
|
SELECT count(*) FROM bittmp WHERE a < '011011000100010111011000110000100';
|
|
|
|
SELECT count(*) FROM bittmp WHERE a <= '011011000100010111011000110000100';
|
|
|
|
SELECT count(*) FROM bittmp WHERE a = '011011000100010111011000110000100';
|
|
|
|
SELECT count(*) FROM bittmp WHERE a >= '011011000100010111011000110000100';
|
|
|
|
SELECT count(*) FROM bittmp WHERE a > '011011000100010111011000110000100';
|
|
|
|
-- Test index-only scans
|
|
SET enable_bitmapscan=off;
|
|
EXPLAIN (COSTS OFF)
|
|
SELECT a FROM bittmp WHERE a BETWEEN '1000000' and '1000001';
|