mirror of
https://github.com/postgres/postgres.git
synced 2025-10-31 10:30:33 +03:00
d92b1cdbab
This reverts commit 9f984ba6d2.
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.3 KiB
SQL
38 lines
1.3 KiB
SQL
-- timestamp check
|
|
|
|
CREATE TABLE timestamptmp (a timestamp);
|
|
|
|
\copy timestamptmp from 'data/timestamp.data'
|
|
|
|
SET enable_seqscan=on;
|
|
|
|
SELECT count(*) FROM timestamptmp WHERE a < '2004-10-26 08:55:08';
|
|
|
|
SELECT count(*) FROM timestamptmp WHERE a <= '2004-10-26 08:55:08';
|
|
|
|
SELECT count(*) FROM timestamptmp WHERE a = '2004-10-26 08:55:08';
|
|
|
|
SELECT count(*) FROM timestamptmp WHERE a >= '2004-10-26 08:55:08';
|
|
|
|
SELECT count(*) FROM timestamptmp WHERE a > '2004-10-26 08:55:08';
|
|
|
|
SELECT a, a <-> '2004-10-26 08:55:08' FROM timestamptmp ORDER BY a <-> '2004-10-26 08:55:08' LIMIT 3;
|
|
|
|
CREATE INDEX timestampidx ON timestamptmp USING gist ( a );
|
|
|
|
SET enable_seqscan=off;
|
|
|
|
SELECT count(*) FROM timestamptmp WHERE a < '2004-10-26 08:55:08'::timestamp;
|
|
|
|
SELECT count(*) FROM timestamptmp WHERE a <= '2004-10-26 08:55:08'::timestamp;
|
|
|
|
SELECT count(*) FROM timestamptmp WHERE a = '2004-10-26 08:55:08'::timestamp;
|
|
|
|
SELECT count(*) FROM timestamptmp WHERE a >= '2004-10-26 08:55:08'::timestamp;
|
|
|
|
SELECT count(*) FROM timestamptmp WHERE a > '2004-10-26 08:55:08'::timestamp;
|
|
|
|
EXPLAIN (COSTS OFF)
|
|
SELECT a, a <-> '2004-10-26 08:55:08' FROM timestamptmp ORDER BY a <-> '2004-10-26 08:55:08' LIMIT 3;
|
|
SELECT a, a <-> '2004-10-26 08:55:08' FROM timestamptmp ORDER BY a <-> '2004-10-26 08:55:08' LIMIT 3;
|