8a859691d5
Fix still another bug in commit 35fcb1b3d: it failed to fully initialize the SortSupport states it introduced to allow the executor to re-check ORDER BY expressions containing distance operators. That led to a null pointer dereference if the sortsupport code tried to use ssup_cxt. The problem only manifests in narrow cases, explaining the lack of previous field reports. It requires a GiST-indexable distance operator that lacks SortSupport and is on a pass-by-ref data type, which among core+contrib seems to be only btree_gist's interval opclass; and it requires the scan to be done as an IndexScan not an IndexOnlyScan, which explains how btree_gist's regression test didn't catch it. Per bug #14134 from Jihyun Yu. Peter Geoghegan Report: <20160511154904.2603.43889@wrigleys.postgresql.org>
44 lines
1.4 KiB
SQL
44 lines
1.4 KiB
SQL
-- interval check
|
|
|
|
CREATE TABLE intervaltmp (a interval);
|
|
|
|
\copy intervaltmp from 'data/interval.data'
|
|
|
|
SET enable_seqscan=on;
|
|
|
|
SELECT count(*) FROM intervaltmp WHERE a < '199 days 21:21:23';
|
|
|
|
SELECT count(*) FROM intervaltmp WHERE a <= '199 days 21:21:23';
|
|
|
|
SELECT count(*) FROM intervaltmp WHERE a = '199 days 21:21:23';
|
|
|
|
SELECT count(*) FROM intervaltmp WHERE a >= '199 days 21:21:23';
|
|
|
|
SELECT count(*) FROM intervaltmp WHERE a > '199 days 21:21:23';
|
|
|
|
SELECT a, a <-> '199 days 21:21:23' FROM intervaltmp ORDER BY a <-> '199 days 21:21:23' LIMIT 3;
|
|
|
|
CREATE INDEX intervalidx ON intervaltmp USING gist ( a );
|
|
|
|
SET enable_seqscan=off;
|
|
|
|
SELECT count(*) FROM intervaltmp WHERE a < '199 days 21:21:23'::interval;
|
|
|
|
SELECT count(*) FROM intervaltmp WHERE a <= '199 days 21:21:23'::interval;
|
|
|
|
SELECT count(*) FROM intervaltmp WHERE a = '199 days 21:21:23'::interval;
|
|
|
|
SELECT count(*) FROM intervaltmp WHERE a >= '199 days 21:21:23'::interval;
|
|
|
|
SELECT count(*) FROM intervaltmp WHERE a > '199 days 21:21:23'::interval;
|
|
|
|
EXPLAIN (COSTS OFF)
|
|
SELECT a, a <-> '199 days 21:21:23' FROM intervaltmp ORDER BY a <-> '199 days 21:21:23' LIMIT 3;
|
|
SELECT a, a <-> '199 days 21:21:23' FROM intervaltmp ORDER BY a <-> '199 days 21:21:23' LIMIT 3;
|
|
|
|
SET enable_indexonlyscan=off;
|
|
|
|
EXPLAIN (COSTS OFF)
|
|
SELECT a, a <-> '199 days 21:21:23' FROM intervaltmp ORDER BY a <-> '199 days 21:21:23' LIMIT 3;
|
|
SELECT a, a <-> '199 days 21:21:23' FROM intervaltmp ORDER BY a <-> '199 days 21:21:23' LIMIT 3;
|