Age | Commit message (Collapse) | Author | |
---|---|---|---|
2016-06-05 | Properly initialize SortSupport for ORDER BY rechecks in nodeIndexscan.c. | Tom Lane | |
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> | |||
2011-03-02 | Add KNNGIST support to contrib/btree_gist. | Tom Lane | |
This extends GiST's support for nearest-neighbor searches to many of the standard data types. Teodor Sigaev | |||
2010-08-19 | Remove extra newlines at end and beginning of files, add missing newlines | Peter Eisentraut | |
at end of files. | |||
2004-05-28 | New version. Add support for int2, int8, float4, float8, timestamp ↵ | Teodor Sigaev | |
with/without time zone, time with/without time zone, date, interval, oid, money and macaddr, char, varchar/text, bytea, numeric, bit, varbit, inet/cidr types for GiST |