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.
38 lines
970 B
SQL
38 lines
970 B
SQL
-- char check
|
|
|
|
CREATE TABLE chartmp (a char(32));
|
|
|
|
\copy chartmp from 'data/char.data'
|
|
|
|
SET enable_seqscan=on;
|
|
|
|
SELECT count(*) FROM chartmp WHERE a < '31b0'::char(32);
|
|
|
|
SELECT count(*) FROM chartmp WHERE a <= '31b0'::char(32);
|
|
|
|
SELECT count(*) FROM chartmp WHERE a = '31b0'::char(32);
|
|
|
|
SELECT count(*) FROM chartmp WHERE a >= '31b0'::char(32);
|
|
|
|
SELECT count(*) FROM chartmp WHERE a > '31b0'::char(32);
|
|
|
|
CREATE INDEX charidx ON chartmp USING GIST ( a );
|
|
|
|
SET enable_seqscan=off;
|
|
|
|
SELECT count(*) FROM chartmp WHERE a < '31b0'::char(32);
|
|
|
|
SELECT count(*) FROM chartmp WHERE a <= '31b0'::char(32);
|
|
|
|
SELECT count(*) FROM chartmp WHERE a = '31b0'::char(32);
|
|
|
|
SELECT count(*) FROM chartmp WHERE a >= '31b0'::char(32);
|
|
|
|
SELECT count(*) FROM chartmp WHERE a > '31b0'::char(32);
|
|
|
|
-- Test index-only scans
|
|
SET enable_bitmapscan=off;
|
|
EXPLAIN (COSTS OFF)
|
|
SELECT * FROM chartmp WHERE a BETWEEN '31a' AND '31c';
|
|
SELECT * FROM chartmp WHERE a BETWEEN '31a' AND '31c';
|