From 83723bf0b96b043b849c747dc2dbb1c85a56f6f8 Mon Sep 17 00:00:00 2001 From: Lakshmi N 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(target [ ... ]) TID_SCAN(target [ ... ]) INDEX_SCAN(target index_name [ ... ]) INDEX_ONLY_SCAN(target index_name [ ... ]) -FOREIGN_SCAN((target [ ... ]) [ ... ]) +FOREIGN_JOIN((target [ ... ]) [ ... ]) BITMAP_HEAP_SCAN(target [ ... ]) DO_NOT_SCAN(target [ ... ]) @@ -288,11 +288,11 @@ DO_NOT_SCAN(target [ ... ]) - FOREIGN_SCAN specifies that a join between two or + FOREIGN_JOIN 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 Foreign Scan. - Specifying FOREIGN_SCAN for a single foreign table is - neither necessary nor permissible: a Foreign Scan will + that it can be implemented as a single Foreign Join. + Specifying FOREIGN_JOIN for a single foreign table is + neither necessary nor permissible: a Foreign Join will need to be used regardless. If you want to prevent a join from being pushed down, consider using the JOIN_ORDER tag for that purpose. @@ -395,7 +395,7 @@ join_method_name(join_method_item [ ... ]) where join_method_name is: -{ 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 } and join_method_item is: -- 2.34.1