]> git.ipfire.org Git - thirdparty/postgresql.git/commitdiff
doc: Fix a couple of mistakes in pgplanadvice.sgml
authorRobert Haas <rhaas@postgresql.org>
Mon, 13 Apr 2026 16:45:57 +0000 (12:45 -0400)
committerRobert Haas <rhaas@postgresql.org>
Mon, 13 Apr 2026 16:45:57 +0000 (12:45 -0400)
It said FOREIGN_SCAN where it should say FOREIGN_JOIN.

NESTED_LOOP_MEMOIZE was mistakenly omitted from the list of join
methods.

Author: Lakshmi N <lakshmin.jhs@gmail.com>
Reviewed-by: jie wang <jugierwang@gmail.com>
Discussion: http://postgr.es/m/CA+3i_M-mo7Of=Pn8WzRfJLt=fc=gDTn1oOdj8v8BEtgXh9ZMCg@mail.gmail.com

doc/src/sgml/pgplanadvice.sgml

index c3e1ccb60a29e6fb3c23ab17a94b25e93cfbc3d8..73155461c0bab2ebdbd601391df1cc1356d1a9cb 100644 (file)
@@ -266,7 +266,7 @@ SEQ_SCAN(<replaceable>target</replaceable> [ ... ])
 TID_SCAN(<replaceable>target</replaceable> [ ... ])
 INDEX_SCAN(<replaceable>target</replaceable> <replaceable>index_name</replaceable> [ ... ])
 INDEX_ONLY_SCAN(<replaceable>target</replaceable> <replaceable>index_name</replaceable> [ ... ])
-FOREIGN_SCAN((<replaceable>target</replaceable> [ ... ]) [ ... ])
+FOREIGN_JOIN((<replaceable>target</replaceable> [ ... ]) [ ... ])
 BITMAP_HEAP_SCAN(<replaceable>target</replaceable> [ ... ])
 DO_NOT_SCAN(<replaceable>target</replaceable> [ ... ])</synopsis>
 
@@ -288,10 +288,10 @@ DO_NOT_SCAN(<replaceable>target</replaceable> [ ... ])</synopsis>
    </para>
 
    <para>
-    <literal>FOREIGN_SCAN</literal> specifies that a join between two or
+    <literal>FOREIGN_JOIN</literal> specifies that a join between two or
     more foreign tables should be pushed down to a remote server so
     that it can be implemented as a single <literal>Foreign Scan</literal>.
-    Specifying <literal>FOREIGN_SCAN</literal> for a single foreign table is
+    Specifying <literal>FOREIGN_JOIN</literal> for a single foreign table is
     neither necessary nor permissible: a <literal>Foreign Scan</literal> will
     need to be used regardless. If you want to prevent a join from being
     pushed down, consider using the <literal>JOIN_ORDER</literal> tag for
@@ -395,7 +395,7 @@ join_method_name(<replaceable>join_method_item</replaceable> [ ... ])
 
 <phrase>where <replaceable>join_method_name</replaceable> is:</phrase>
 
-{ MERGE_JOIN_MATERIALIZE | MERGE_JOIN_PLAIN | NESTED_LOOP_MATERIALIZE | NESTED_LOOP_PLAIN | HASH_JOIN }
+{ MERGE_JOIN_MATERIALIZE | MERGE_JOIN_PLAIN | NESTED_LOOP_MATERIALIZE | NESTED_LOOP_MEMOIZE | NESTED_LOOP_PLAIN | HASH_JOIN }
 
 <phrase>and <replaceable>join_method_item</replaceable> is:</phrase>