@@ -900,8 +900,8 @@ above, plus a relids set, which allows there to be more than one upperrel
900900of the same kind. We use NULL for the relids if there's no need for more
901901than one upperrel of the same kind. Currently, in fact, the relids set
902902is vestigial because it's always NULL, but that's expected to change in
903- future. For example, in planning set operations, we might need the relids
904- to denote which subset of the leaf SELECTs has been combined in a
903+ the future. For example, in planning set operations, we might need the
904+ relids to denote which subset of the leaf SELECTs has been combined in a
905905particular group of Paths that are competing with each other.
906906
907907The result of subquery_planner() is always returned as a set of Paths
@@ -974,5 +974,5 @@ One of the keys to making parallel query effective is to run as much of
974974the query in parallel as possible. Therefore, we expect it to generally
975975be desirable to postpone the Gather stage until as near to the top of the
976976plan as possible. Expanding the range of cases in which more work can be
977- pushed below the Gather (andcostly them accurately) is likely to keep us
977+ pushed below the Gather (andcosting them accurately) is likely to keep us
978978busy for a long time to come.