aboutsummaryrefslogtreecommitdiff
path: root/src/backend/access/gist
diff options
context:
space:
mode:
authorHeikki Linnakangas <heikki.linnakangas@iki.fi>2016-09-20 11:38:25 +0300
committerHeikki Linnakangas <heikki.linnakangas@iki.fi>2016-09-20 11:38:25 +0300
commit45310221a9afccd98e78813459472370ade9dc4c (patch)
treeb44ad2bee06d77f7cfe8906a8b5630dcd8d61c3c /src/backend/access/gist
parent40c3fe4980e73acb0db75a3c737a4a52e09d4cf4 (diff)
downloadpostgresql-45310221a9afccd98e78813459472370ade9dc4c.tar.gz
postgresql-45310221a9afccd98e78813459472370ade9dc4c.zip
Fix outdated comments, GIST search queue is not an RBTree anymore.
The GiST search queue is implemented as a pairing heap rather than as Red-Black Tree, since 9.5 (commit e7032610). I neglected these comments in that commit.
Diffstat (limited to 'src/backend/access/gist')
-rw-r--r--src/backend/access/gist/gistscan.c4
1 files changed, 2 insertions, 2 deletions
diff --git a/src/backend/access/gist/gistscan.c b/src/backend/access/gist/gistscan.c
index ba611ee490a..2526a3965c4 100644
--- a/src/backend/access/gist/gistscan.c
+++ b/src/backend/access/gist/gistscan.c
@@ -125,7 +125,7 @@ gistrescan(IndexScanDesc scan, ScanKey key, int nkeys,
* which is created on the second call and reset on later calls. Thus, in
* the common case where a scan is only rescan'd once, we just put the
* queue in scanCxt and don't pay the overhead of making a second memory
- * context. If we do rescan more than once, the first RBTree is just left
+ * context. If we do rescan more than once, the first queue is just left
* for dead until end of scan; this small wastage seems worth the savings
* in the common case.
*/
@@ -181,7 +181,7 @@ gistrescan(IndexScanDesc scan, ScanKey key, int nkeys,
ALLOCSET_DEFAULT_SIZES);
}
- /* create new, empty RBTree for search queue */
+ /* create new, empty pairing heap for search queue */
oldCxt = MemoryContextSwitchTo(so->queueCxt);
so->queue = pairingheap_allocate(pairingheap_GISTSearchItem_cmp, scan);
MemoryContextSwitchTo(oldCxt);