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
1014 B
SQL
38 lines
1014 B
SQL
-- money check
|
|
|
|
CREATE TABLE moneytmp (a money);
|
|
|
|
\copy moneytmp from 'data/cash.data'
|
|
|
|
SET enable_seqscan=on;
|
|
|
|
SELECT count(*) FROM moneytmp WHERE a < '22649.64';
|
|
|
|
SELECT count(*) FROM moneytmp WHERE a <= '22649.64';
|
|
|
|
SELECT count(*) FROM moneytmp WHERE a = '22649.64';
|
|
|
|
SELECT count(*) FROM moneytmp WHERE a >= '22649.64';
|
|
|
|
SELECT count(*) FROM moneytmp WHERE a > '22649.64';
|
|
|
|
SELECT a, a <-> '21472.79' FROM moneytmp ORDER BY a <-> '21472.79' LIMIT 3;
|
|
|
|
CREATE INDEX moneyidx ON moneytmp USING gist ( a );
|
|
|
|
SET enable_seqscan=off;
|
|
|
|
SELECT count(*) FROM moneytmp WHERE a < '22649.64'::money;
|
|
|
|
SELECT count(*) FROM moneytmp WHERE a <= '22649.64'::money;
|
|
|
|
SELECT count(*) FROM moneytmp WHERE a = '22649.64'::money;
|
|
|
|
SELECT count(*) FROM moneytmp WHERE a >= '22649.64'::money;
|
|
|
|
SELECT count(*) FROM moneytmp WHERE a > '22649.64'::money;
|
|
|
|
EXPLAIN (COSTS OFF)
|
|
SELECT a, a <-> '21472.79' FROM moneytmp ORDER BY a <-> '21472.79' LIMIT 3;
|
|
SELECT a, a <-> '21472.79' FROM moneytmp ORDER BY a <-> '21472.79' LIMIT 3;
|