you were absolutely right - it was all to do with multiple call sites -
the postgres version was just a red herring.
Thanks for your help & all the best,
Dave
On 17/10/2019 10:04, Tom Lane wrote:
David Conlin writes:
Does anyone know if there's been a change in the way value
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,
It seems like no-one has any ideas on this - does anyone know anywhere
else I can try to look/ask to find out more?
Is it possible that this is a bug?
Thanks
Dave
On 16/01/2019 11:31, David Conlin wrote:
Hi folks -
I'm having trouble understanding what some of the stats mean i
Hi folks -
I'm having trouble understanding what some of the stats mean in the
execution plan output when parallel workers are used. I've tried to read
up about it, but I haven't been able to find anything that explains what
I'm seeing. Apologies in advance if there's documentation I've been t
