pgsql: Don't call IS_DUMMY_REL() when cheapest_total_path might be junk

From: Robert Haas <rhaas(at)postgresql(dot)org>
To: pgsql-committers(at)lists(dot)postgresql(dot)org
Subject: pgsql: Don't call IS_DUMMY_REL() when cheapest_total_path might be junk
Date: 2018-03-30 15:45:33
Message-ID: E1f1wDd-00057z-IJ@gemulon.postgresql.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-committers

Don't call IS_DUMMY_REL() when cheapest_total_path might be junk.

Unlike the previous coding, this might result in a Gather per Append
subplan when the target list is parallel-restricted, but such a plan
is probably worth considering in that case, since a single Gather
on top of the entire Append is impossible.

Per Andres Freund and the buildfarm.

Discussion: http://postgr.es/m/20180330050351.bmxx4cdtz67czjda@alap3.anarazel.de

Branch
------
master

Details
-------
https://git.postgresql.org/pg/commitdiff/96030f9a481a78483945447e122a387902a4549b

Modified Files
--------------
src/backend/optimizer/plan/planner.c | 32 +++++++++++++++++---------------
1 file changed, 17 insertions(+), 15 deletions(-)

Browse pgsql-committers by date

  From Date Subject
Next Message Robert Haas 2018-03-30 15:45:43 Re: pgsql: Rewrite the code that applies scan/join targets to paths.
Previous Message Bruce Momjian 2018-03-30 15:18:17 pgsql: docs: add parameter with brackets around varbit()