diff --git a/doc/src/sgml/perform.sgml b/doc/src/sgml/perform.sgml index ff689b6524..e3912bdbf2 100644 --- a/doc/src/sgml/perform.sgml +++ b/doc/src/sgml/perform.sgml @@ -578,6 +578,33 @@ WHERE t1.unique1 < 100 AND t1.unique2 = t2.unique2; discussed below. + + When using the enable/disable flags to disable plan node types, many of + the flags only discourage the use of the corresponding plan node and don't + outright disallow the planner's ability to use the plan node type. This + is done so that the planner still maintains the ability to form a plan for + a given query. Otherwise, certain queries could be executed when certain + plan node types are disabled. This means it is possible that the planner + chooses a plan using a node that has been disabled. When this happens, + the EXPLAIN output will indicate this fact. + + +SET enable_seqscan = off; +EXPLAIN SELECT * FROM unit; + + QUERY PLAN +--------------------------------------------------------- + Seq Scan on unit (cost=0.00..21.30 rows=1130 width=44) + Disabled: true + + + + + Because the unit table has no indexes, there is no + other means to read the table data, so the sequential scan is the only + option available to the query planner. + + subplan