Change in CTE treatment in query plans?

From: David Conlin <dc345(at)cantab(dot)net>
To: pgsql-performance(at)lists(dot)postgresql(dot)org
Subject: Change in CTE treatment in query plans?
Date: 2019-10-15 11:28:19
Message-ID: 560a2cb6-556f-67a7-3676-dba69f2c69e6@cantab.net
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-performance

Hi folks -

Does anyone know if there's been a change in the way values for CTEs are
displayed in query plans?

I think that it used to be the case that, for keys that include the
values of child nodes values (eg "Shared Hit Blocks", or "Actual Total
Time"), CTE scans included the CTE itself, even if it wasn't included as
one of its children in the plan. If you didn't subtract the CTE scan,
you would see surprising things, like sort operations reading table
data, or the total time of the nodes in a single-threaded query plan
adding up to significantly more than 100% of the total query time.

Now (I think since v11, but I'm not sure), it looks like these values
only include the children listed in the plan. For example, I've seen CTE
scans that have smaller times and buffers values than the CTE itself,
which couldn't be true if the CTE was included in the scan.

I'm much less sure, but I *think* the same is also true of other
InitPlan nodes - for example, if a node includes the filter "value >
$1", its time and buffers used to (but no longer does) include the total
for the InitPlan node which returned the value "$1".

Am I way off base with this, or did this change happen, and if so, am I
right in thinking that it was changed in v11?

Thanks in advance

Dave

Responses

Browse pgsql-performance by date

  From Date Subject
Next Message dangal 2019-10-16 17:37:37 Re: pg_stat_bgwriter
Previous Message Tomas Vondra 2019-10-15 00:39:35 Re: pg_stat_bgwriter