@@ -896,15 +896,16 @@ EXPLAIN ANALYZE SELECT * FROM tenk1 WHERE unique1 < 100 AND unique2 > 9000
896896 </para>
897897
898898 <para>
899- Generally, the <command>EXPLAIN</command> output will display details for
900- every plan node which was generated by the query planner. However, there
901- are cases where the executor is able to determine that certain nodes are
902- not required; currently, the only node types to support this are the
903- <literal>Append</literal> and <literal>MergeAppend</literal> nodes. These
904- node types have the ability to discard subnodes which they are able to
905- determine won't contain any records required by the query. It is possible
906- to determine that nodes have been removed in this way by the presence of a
907- "Subplans Removed" property in the <command>EXPLAIN</command> output.
899+ Normally, <command>EXPLAIN</command> will display every plan node
900+ created by the planner. However, there are cases where the executor
901+ can determine that certain nodes need not be executed because they
902+ cannot produce any rows, based on parameter values that were not
903+ available at planning time. (Currently this can only happen for child
904+ nodes of an Append or MergeAppend node that is scanning a partitioned
905+ table.) When this happens, those plan nodes are omitted from
906+ the <command>EXPLAIN</command> output and a <literal>Subplans
907+ Removed: <replaceable>N</replaceable></literal> annotation appears
908+ instead.
908909 </para>
909910 </sect2>
910911