v2-0001-DOCS-Update-pgplanadvice-tags-for-FOREIGN_JOIN-an.patch
application/octet-stream
Filename: v2-0001-DOCS-Update-pgplanadvice-tags-for-FOREIGN_JOIN-an.patch
Type: application/octet-stream
Part: 0
Patch
Same data as JSON:
GET /api/v1/attachments/:id/patch
the parsed metadata as JSON — format, series position, per-file stats; never the diff bytes.
API reference →
Format: format-patch
Series: patch v2-0001
Subject: DOCS: Update pgplanadvice tags for FOREIGN_JOIN and NESTED_LOOP_MEMOIZE
| File | + | − |
|---|---|---|
| doc/src/sgml/pgplanadvice.sgml | 6 | 6 |
From 83723bf0b96b043b849c747dc2dbb1c85a56f6f8 Mon Sep 17 00:00:00 2001
From: Lakshmi N <lakshmin.jhs@gmail.com>
Date: Tue, 7 Apr 2026 23:58:15 -0700
Subject: [PATCH v2] DOCS: Update pgplanadvice tags for FOREIGN_JOIN and
NESTED_LOOP_MEMOIZE
---
doc/src/sgml/pgplanadvice.sgml | 12 ++++++------
1 file changed, 6 insertions(+), 6 deletions(-)
diff --git a/doc/src/sgml/pgplanadvice.sgml b/doc/src/sgml/pgplanadvice.sgml
index c3e1ccb60a2..e8f5edec874 100644
--- a/doc/src/sgml/pgplanadvice.sgml
+++ b/doc/src/sgml/pgplanadvice.sgml
@@ -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,11 +288,11 @@ 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
- neither necessary nor permissible: a <literal>Foreign Scan</literal> will
+ that it can be implemented as a single <literal>Foreign Join</literal>.
+ Specifying <literal>FOREIGN_JOIN</literal> for a single foreign table is
+ neither necessary nor permissible: a <literal>Foreign Join</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
that purpose.
@@ -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>
--
2.34.1