From: David Rowley <drowley@postgresql.org>
Date: Sun, 9 Jul 2023 04:14:00 +0000 (+1200)
Subject: Doc: update old reference to "result cache"
X-Git-Url: http://git.postgresql.org/gitweb/-?a=commitdiff_plain;h=c23e7ea4d6a44cd0f6948d362a8477f14a3f849c;p=users%2Frhaas%2Fpostgres.git

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
---

diff --git a/doc/src/sgml/config.sgml b/doc/src/sgml/config.sgml
index c9fa6cd9c7..57c4dcee93 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