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
890 B
SQL
38 lines
890 B
SQL
-- int4 check
|
|
|
|
CREATE TABLE int4tmp (a int4);
|
|
|
|
\copy int4tmp from 'data/int2.data'
|
|
|
|
SET enable_seqscan=on;
|
|
|
|
SELECT count(*) FROM int4tmp WHERE a < 237;
|
|
|
|
SELECT count(*) FROM int4tmp WHERE a <= 237;
|
|
|
|
SELECT count(*) FROM int4tmp WHERE a = 237;
|
|
|
|
SELECT count(*) FROM int4tmp WHERE a >= 237;
|
|
|
|
SELECT count(*) FROM int4tmp WHERE a > 237;
|
|
|
|
SELECT a, a <-> '237' FROM int4tmp ORDER BY a <-> '237' LIMIT 3;
|
|
|
|
CREATE INDEX int4idx ON int4tmp USING gist ( a );
|
|
|
|
SET enable_seqscan=off;
|
|
|
|
SELECT count(*) FROM int4tmp WHERE a < 237::int4;
|
|
|
|
SELECT count(*) FROM int4tmp WHERE a <= 237::int4;
|
|
|
|
SELECT count(*) FROM int4tmp WHERE a = 237::int4;
|
|
|
|
SELECT count(*) FROM int4tmp WHERE a >= 237::int4;
|
|
|
|
SELECT count(*) FROM int4tmp WHERE a > 237::int4;
|
|
|
|
EXPLAIN (COSTS OFF)
|
|
SELECT a, a <-> '237' FROM int4tmp ORDER BY a <-> '237' LIMIT 3;
|
|
SELECT a, a <-> '237' FROM int4tmp ORDER BY a <-> '237' LIMIT 3;
|