Tom Lane 8a859691d5 Properly initialize SortSupport for ORDER BY rechecks in nodeIndexscan.c. ... 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>		2016-06-05 11:53:06 -04:00
..
bit.sql	Add index-only scan support to btree_gist.	2015-03-27 23:35:16 +02:00
bytea.sql	Add index-only scan support to btree_gist.	2015-03-27 23:35:16 +02:00
cash.sql
char.sql	Add index-only scan support to btree_gist.	2015-03-27 23:35:16 +02:00
cidr.sql
date.sql
float4.sql
float8.sql
inet.sql
init.sql
int2.sql
int4.sql
int8.sql
interval.sql	Properly initialize SortSupport for ORDER BY rechecks in nodeIndexscan.c.	2016-06-05 11:53:06 -04:00
macaddr.sql	Add index-only scan support to btree_gist.	2015-03-27 23:35:16 +02:00
not_equal.sql	Ensure plan stability in contrib/btree_gist regression test.	2016-05-12 20:04:38 -04:00
numeric.sql	Add index-only scan support to btree_gist.	2015-03-27 23:35:16 +02:00
oid.sql
text.sql	Add index-only scan support to btree_gist.	2015-03-27 23:35:16 +02:00
time.sql
timestamp.sql
timestamptz.sql
timetz.sql
varbit.sql	Add index-only scan support to btree_gist.	2015-03-27 23:35:16 +02:00
varchar.sql