mirror of
https://github.com/postgres/postgres.git
synced 2025-10-30 00:04:49 -04: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
1022 B
SQL
38 lines
1022 B
SQL
-- date check
|
|
|
|
CREATE TABLE datetmp (a date);
|
|
|
|
\copy datetmp from 'data/date.data'
|
|
|
|
SET enable_seqscan=on;
|
|
|
|
SELECT count(*) FROM datetmp WHERE a < '2001-02-13';
|
|
|
|
SELECT count(*) FROM datetmp WHERE a <= '2001-02-13';
|
|
|
|
SELECT count(*) FROM datetmp WHERE a = '2001-02-13';
|
|
|
|
SELECT count(*) FROM datetmp WHERE a >= '2001-02-13';
|
|
|
|
SELECT count(*) FROM datetmp WHERE a > '2001-02-13';
|
|
|
|
SELECT a, a <-> '2001-02-13' FROM datetmp ORDER BY a <-> '2001-02-13' LIMIT 3;
|
|
|
|
CREATE INDEX dateidx ON datetmp USING gist ( a );
|
|
|
|
SET enable_seqscan=off;
|
|
|
|
SELECT count(*) FROM datetmp WHERE a < '2001-02-13'::date;
|
|
|
|
SELECT count(*) FROM datetmp WHERE a <= '2001-02-13'::date;
|
|
|
|
SELECT count(*) FROM datetmp WHERE a = '2001-02-13'::date;
|
|
|
|
SELECT count(*) FROM datetmp WHERE a >= '2001-02-13'::date;
|
|
|
|
SELECT count(*) FROM datetmp WHERE a > '2001-02-13'::date;
|
|
|
|
EXPLAIN (COSTS OFF)
|
|
SELECT a, a <-> '2001-02-13' FROM datetmp ORDER BY a <-> '2001-02-13' LIMIT 3;
|
|
SELECT a, a <-> '2001-02-13' FROM datetmp ORDER BY a <-> '2001-02-13' LIMIT 3;
|