mirror of
https://github.com/postgres/postgres.git
synced 2026-10-23 13:29:09 +03:00
dbb9bac594
To perform cross-type index scans with a timestamp index and a timestamptz comparison value, btree_gin must convert the timestamptz to timestamp to establish the starting point for the indexscan. This is hazardous because timestamp_cmp_timestamptz is actually defined to upconvert the timestamp to timestamptz and then compare timestamptz's. When dealing with ambiguous timestamps near a fall-back DST transition, the value may not round-trip, leading to selecting a scan start point that misses some index entries that should match. To fix that, move the converted value back an hour at a time until it's clearly <= the given comparison value. (We could try to be smarter, but this way seems more certain to work across all possible DST behaviors.) Another hazard is that for timestamptz's that are finite but close to the upper range limit, the conversion may produce timestamp +Infinity, again comparing greater than the given value. It's less clear whether this can lead to missing matching values in practice, but it would at least risk making the aforesaid correction loop very slow. So replace +Infinity by the maximum finite timestamp. The reverse case of timestamptz index and timestamp comparison value is not at risk because upconverting the timestamp stays consistent with what timestamptz_cmp_timestamp will do. Also, while date-vs-timestamptz could theoretically be at risk, the conversion error would have to be a full day which seems not to occur in reality. Author: shihao zhong <zhong950419@gmail.com> Reviewed-by: Tom Lane <tgl@sss.pgh.pa.us> Discussion: https://postgr.es/m/CAGRkXqQio=7PWgTfKvjyQY9-7A_0A36E3put1gxJeDypgqFSzw@mail.gmail.com Backpatch-through: 19
83 lines
3.9 KiB
SQL
83 lines
3.9 KiB
SQL
set enable_seqscan=off;
|
|
|
|
CREATE TABLE test_timestamp (
|
|
i timestamp
|
|
);
|
|
|
|
INSERT INTO test_timestamp VALUES
|
|
( '2004-10-26 03:55:08' ),
|
|
( '2004-10-26 04:55:08' ),
|
|
( '2004-10-26 05:55:08' ),
|
|
( '2004-10-26 08:55:08' ),
|
|
( '2004-10-27 09:55:08' ),
|
|
( '2004-10-27 10:55:08' )
|
|
;
|
|
|
|
CREATE INDEX idx_timestamp ON test_timestamp USING gin (i);
|
|
|
|
SELECT * FROM test_timestamp WHERE i<'2004-10-26 08:55:08'::timestamp ORDER BY i;
|
|
SELECT * FROM test_timestamp WHERE i<='2004-10-26 08:55:08'::timestamp ORDER BY i;
|
|
SELECT * FROM test_timestamp WHERE i='2004-10-26 08:55:08'::timestamp ORDER BY i;
|
|
SELECT * FROM test_timestamp WHERE i>='2004-10-26 08:55:08'::timestamp ORDER BY i;
|
|
SELECT * FROM test_timestamp WHERE i>'2004-10-26 08:55:08'::timestamp ORDER BY i;
|
|
|
|
explain (costs off)
|
|
SELECT * FROM test_timestamp WHERE i<'2004-10-27'::date ORDER BY i;
|
|
|
|
SELECT * FROM test_timestamp WHERE i<'2004-10-27'::date ORDER BY i;
|
|
SELECT * FROM test_timestamp WHERE i<='2004-10-27'::date ORDER BY i;
|
|
SELECT * FROM test_timestamp WHERE i='2004-10-27'::date ORDER BY i;
|
|
SELECT * FROM test_timestamp WHERE i>='2004-10-27'::date ORDER BY i;
|
|
SELECT * FROM test_timestamp WHERE i>'2004-10-27'::date ORDER BY i;
|
|
|
|
explain (costs off)
|
|
SELECT * FROM test_timestamp WHERE i<'2004-10-26 08:55:08'::timestamptz ORDER BY i;
|
|
|
|
SELECT * FROM test_timestamp WHERE i<'2004-10-26 08:55:08'::timestamptz ORDER BY i;
|
|
SELECT * FROM test_timestamp WHERE i<='2004-10-26 08:55:08'::timestamptz ORDER BY i;
|
|
SELECT * FROM test_timestamp WHERE i='2004-10-26 08:55:08'::timestamptz ORDER BY i;
|
|
SELECT * FROM test_timestamp WHERE i>='2004-10-26 08:55:08'::timestamptz ORDER BY i;
|
|
SELECT * FROM test_timestamp WHERE i>'2004-10-26 08:55:08'::timestamptz ORDER BY i;
|
|
|
|
-- Check endpoint and out-of-range cases
|
|
|
|
INSERT INTO test_timestamp VALUES ('-infinity'), ('infinity');
|
|
SELECT gin_clean_pending_list('idx_timestamp');
|
|
|
|
SELECT * FROM test_timestamp WHERE i<'-infinity'::date ORDER BY i;
|
|
SELECT * FROM test_timestamp WHERE i<='-infinity'::date ORDER BY i;
|
|
SELECT * FROM test_timestamp WHERE i='-infinity'::date ORDER BY i;
|
|
SELECT * FROM test_timestamp WHERE i>='-infinity'::date ORDER BY i;
|
|
SELECT * FROM test_timestamp WHERE i>'-infinity'::date ORDER BY i;
|
|
|
|
SELECT * FROM test_timestamp WHERE i<'infinity'::date ORDER BY i;
|
|
SELECT * FROM test_timestamp WHERE i<='infinity'::date ORDER BY i;
|
|
SELECT * FROM test_timestamp WHERE i='infinity'::date ORDER BY i;
|
|
SELECT * FROM test_timestamp WHERE i>='infinity'::date ORDER BY i;
|
|
SELECT * FROM test_timestamp WHERE i>'infinity'::date ORDER BY i;
|
|
|
|
SELECT * FROM test_timestamp WHERE i<'-infinity'::timestamptz ORDER BY i;
|
|
SELECT * FROM test_timestamp WHERE i<='-infinity'::timestamptz ORDER BY i;
|
|
SELECT * FROM test_timestamp WHERE i='-infinity'::timestamptz ORDER BY i;
|
|
SELECT * FROM test_timestamp WHERE i>='-infinity'::timestamptz ORDER BY i;
|
|
SELECT * FROM test_timestamp WHERE i>'-infinity'::timestamptz ORDER BY i;
|
|
|
|
SELECT * FROM test_timestamp WHERE i<'infinity'::timestamptz ORDER BY i;
|
|
SELECT * FROM test_timestamp WHERE i<='infinity'::timestamptz ORDER BY i;
|
|
SELECT * FROM test_timestamp WHERE i='infinity'::timestamptz ORDER BY i;
|
|
SELECT * FROM test_timestamp WHERE i>='infinity'::timestamptz ORDER BY i;
|
|
SELECT * FROM test_timestamp WHERE i>'infinity'::timestamptz ORDER BY i;
|
|
|
|
-- This PST timestamptz will underflow if converted to timestamp
|
|
SELECT * FROM test_timestamp WHERE i<='4714-11-23 17:00 BC'::timestamptz ORDER BY i;
|
|
SELECT * FROM test_timestamp WHERE i>'4714-11-23 17:00 BC'::timestamptz ORDER BY i;
|
|
|
|
-- Check that we aren't fooled by ambiguous timestamps near a DST transition
|
|
INSERT INTO test_timestamp VALUES
|
|
('2026-11-01 00:50'), ('2026-11-01 01:10'), ('2026-11-01 01:20'),
|
|
('2026-11-01 01:40'), ('2026-11-01 02:10');
|
|
SET TimeZone = 'America/New_York';
|
|
SELECT * FROM test_timestamp WHERE i>='2026-11-01 01:30-04'::timestamptz ORDER BY i;
|
|
SELECT * FROM test_timestamp WHERE i>'2026-11-01 01:30-04'::timestamptz ORDER BY i;
|
|
RESET TimeZone;
|