mirror of
https://github.com/postgres/postgres.git
synced 2025-10-29 22:49:41 +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
990 B
SQL
38 lines
990 B
SQL
-- time check
|
|
|
|
CREATE TABLE timetmp (a time);
|
|
|
|
\copy timetmp from 'data/time.data'
|
|
|
|
SET enable_seqscan=on;
|
|
|
|
SELECT count(*) FROM timetmp WHERE a < '10:57:11';
|
|
|
|
SELECT count(*) FROM timetmp WHERE a <= '10:57:11';
|
|
|
|
SELECT count(*) FROM timetmp WHERE a = '10:57:11';
|
|
|
|
SELECT count(*) FROM timetmp WHERE a >= '10:57:11';
|
|
|
|
SELECT count(*) FROM timetmp WHERE a > '10:57:11';
|
|
|
|
SELECT a, a <-> '10:57:11' FROM timetmp ORDER BY a <-> '10:57:11' LIMIT 3;
|
|
|
|
CREATE INDEX timeidx ON timetmp USING gist ( a );
|
|
|
|
SET enable_seqscan=off;
|
|
|
|
SELECT count(*) FROM timetmp WHERE a < '10:57:11'::time;
|
|
|
|
SELECT count(*) FROM timetmp WHERE a <= '10:57:11'::time;
|
|
|
|
SELECT count(*) FROM timetmp WHERE a = '10:57:11'::time;
|
|
|
|
SELECT count(*) FROM timetmp WHERE a >= '10:57:11'::time;
|
|
|
|
SELECT count(*) FROM timetmp WHERE a > '10:57:11'::time;
|
|
|
|
EXPLAIN (COSTS OFF)
|
|
SELECT a, a <-> '10:57:11' FROM timetmp ORDER BY a <-> '10:57:11' LIMIT 3;
|
|
SELECT a, a <-> '10:57:11' FROM timetmp ORDER BY a <-> '10:57:11' LIMIT 3;
|