aboutsummaryrefslogtreecommitdiff
path: root/src/backend/access/gist/gistscan.c
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:40:20 +0300
commitf0a86dfdb465d4d18b8010000205224733d9848e (patch)
treef5cc1122b07a9980b52e303861a7fb116734c602 /src/backend/access/gist/gistscan.c
parentedb5c4097604c90e12649cdf24accc6052140b78 (diff)
downloadpostgresql-f0a86dfdb465d4d18b8010000205224733d9848e.tar.gz
postgresql-f0a86dfdb465d4d18b8010000205224733d9848e.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/gistscan.c')
-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 ee3289ae8ea..62f1fdd8da2 100644
--- a/src/backend/access/gist/gistscan.c
+++ b/src/backend/access/gist/gistscan.c
@@ -126,7 +126,7 @@ gistrescan(PG_FUNCTION_ARGS)
* 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.
*/
@@ -186,7 +186,7 @@ gistrescan(PG_FUNCTION_ARGS)
ALLOCSET_DEFAULT_MAXSIZE);
}
- /* 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);