mirror of
https://github.com/postgres/postgres.git
synced 2025-04-20 00:42:27 +03:00
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
1.1 KiB
SQL
38 lines
1.1 KiB
SQL
-- int8 check
|
|
|
|
CREATE TABLE int8tmp (a int8);
|
|
|
|
\copy int8tmp from 'data/int8.data'
|
|
|
|
SET enable_seqscan=on;
|
|
|
|
SELECT count(*) FROM int8tmp WHERE a < 464571291354841;
|
|
|
|
SELECT count(*) FROM int8tmp WHERE a <= 464571291354841;
|
|
|
|
SELECT count(*) FROM int8tmp WHERE a = 464571291354841;
|
|
|
|
SELECT count(*) FROM int8tmp WHERE a >= 464571291354841;
|
|
|
|
SELECT count(*) FROM int8tmp WHERE a > 464571291354841;
|
|
|
|
SELECT a, a <-> '464571291354841' FROM int8tmp ORDER BY a <-> '464571291354841' LIMIT 3;
|
|
|
|
CREATE INDEX int8idx ON int8tmp USING gist ( a );
|
|
|
|
SET enable_seqscan=off;
|
|
|
|
SELECT count(*) FROM int8tmp WHERE a < 464571291354841::int8;
|
|
|
|
SELECT count(*) FROM int8tmp WHERE a <= 464571291354841::int8;
|
|
|
|
SELECT count(*) FROM int8tmp WHERE a = 464571291354841::int8;
|
|
|
|
SELECT count(*) FROM int8tmp WHERE a >= 464571291354841::int8;
|
|
|
|
SELECT count(*) FROM int8tmp WHERE a > 464571291354841::int8;
|
|
|
|
EXPLAIN (COSTS OFF)
|
|
SELECT a, a <-> '464571291354841' FROM int8tmp ORDER BY a <-> '464571291354841' LIMIT 3;
|
|
SELECT a, a <-> '464571291354841' FROM int8tmp ORDER BY a <-> '464571291354841' LIMIT 3;
|