aboutsummaryrefslogtreecommitdiff
path: root/doc/src
diff options
context:
space:
mode:
authorDavid Rowley <drowley@postgresql.org>2021-04-01 13:33:23 +1300
committerDavid Rowley <drowley@postgresql.org>2021-04-01 13:33:23 +1300
commit28b3e3905c982c42fb10ee800e6f881e9742c89d (patch)
tree5368a84ddedf0c0da61fc9ec73ea148658821f0b /doc/src
parentb6002a796dc0bfe721db5eaa54ba9d24fd9fd416 (diff)
downloadpostgresql-28b3e3905c982c42fb10ee800e6f881e9742c89d.tar.gz
postgresql-28b3e3905c982c42fb10ee800e6f881e9742c89d.zip
Revert b6002a796
This removes "Add Result Cache executor node". It seems that something weird is going on with the tracking of cache hits and misses as highlighted by many buildfarm animals. It's not yet clear what the problem is as other parts of the plan indicate that the cache did work correctly, it's just the hits and misses that were being reported as 0. This is especially a bad time to have the buildfarm so broken, so reverting before too many more animals go red. Discussion: https://postgr.es/m/CAApHDvq_hydhfovm4=izgWs+C5HqEeRScjMbOgbpC-jRAeK3Yw@mail.gmail.com
Diffstat (limited to 'doc/src')
-rw-r--r--doc/src/sgml/config.sgml24
1 files changed, 2 insertions, 22 deletions
diff --git a/doc/src/sgml/config.sgml b/doc/src/sgml/config.sgml
index 9d87b5097af..d1e2e8c4c32 100644
--- a/doc/src/sgml/config.sgml
+++ b/doc/src/sgml/config.sgml
@@ -1770,9 +1770,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, and
+ hash-based processing of <literal>IN</literal> subqueries.
</para>
<para>
Hash-based operations are generally more sensitive to memory
@@ -4926,25 +4925,6 @@ ANY <replaceable class="parameter">num_sync</replaceable> ( <replaceable class="
</listitem>
</varlistentry>
- <varlistentry id="guc-enable-resultcache" xreflabel="enable_resultcache">
- <term><varname>enable_resultcache</varname> (<type>boolean</type>)
- <indexterm>
- <primary><varname>enable_resultcache</varname> configuration parameter</primary>
- </indexterm>
- </term>
- <listitem>
- <para>
- Enables or disables the query planner's use of result cache plans for
- caching results from parameterized scans inside nested-loop joins.
- This plan type allows scans to the underlying plans to be skipped when
- the results for the current parameters are already in the cache. Less
- commonly looked up results may be evicted from the cache when more
- space is required for new entries. The default is
- <literal>on</literal>.
- </para>
- </listitem>
- </varlistentry>
-
<varlistentry id="guc-enable-mergejoin" xreflabel="enable_mergejoin">
<term><varname>enable_mergejoin</varname> (<type>boolean</type>)
<indexterm>