From 6d8b5f49f0e18a0e8a926a4315c6a70efa34036e Mon Sep 17 00:00:00 2001
From: David Rowley <drowley@postgresql.org>
Date: Sun, 9 Jul 2023 16:14:47 +1200
Subject: [PATCH] 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 6262cb7bb2f..6a14f3b065e 100644
--- a/doc/src/sgml/config.sgml
+++ b/doc/src/sgml/config.sgml
@@ -1889,9 +1889,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