postgres.git / summary / log / commit / refs
commit c23e7ea4d6a44cd0f6948d362a8477f14a3f849c
Author: David Rowley <drowley@postgresql.org>
Date: Sun Jul 09 04:14:00 2023 +0000
First released in: 17.0, 14.9, 15.4, 16.0
Doc: update old reference to "result cache"
During the PostgreSQL 14 cycle, the Memoize executor node was briefly
called "Result Cache" until it was renamed in 83f4fcc65. That commit
missed one reference.
Reported-by: Paul A Jungwirth
Packpatch-through: 14, where Memoize was added
Discussion: https://postgr.es/m/CA+renyX=40YXhsfPTzn13oNOPO3TJ12CK9GX-2P2pvnQiScefA@mail.gmail.com
doc/src/sgml/config.sgml | 5 ++---
1 file changed, 2 insertions(+), 3 deletions(-)
diff --git a/doc/src/sgml/config.sgml b/doc/src/sgml/config.sgml
index c9fa6cd9c76..57c4dcee931 100644
--- a/doc/src/sgml/config.sgml
+++ b/doc/src/sgml/config.sgml
@@ -1891,9 +1891,8 @@ include_dir 'conf.d'
fact in mind when choosing the value. Sort operations are used
for <literal>ORDER BY</literal>, <literal>DISTINCT</literal>,
and merge joins.
- Hash tables are used in hash joins, hash-based aggregation, result
- cache nodes and hash-based processing of <literal>IN</literal>
- subqueries.
+ Hash tables are used in hash joins, hash-based aggregation, memoize
+ nodes and hash-based processing of <literal>IN</literal> subqueries.
</para>
<para>
Hash-based operations are generally more sensitive to memory
[parent: 1aadc504bf47]