Re: Wrong rows estimations with joins of CTEs slows queries by more than factor 500 - Mailing list pgsql-hackers

From David G. Johnston
Subject Re: Wrong rows estimations with joins of CTEs slows queries by more than factor 500
Date
Msg-id CAKFQuwa-pA960B=Ev=6SSqzPv2Pu5BXgZC=J9wYfRB3-MJ1faQ@mail.gmail.com
Whole thread Raw
In response to Re: Wrong rows estimations with joins of CTEs slows queries by more than factor 500  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
On Thursday, November 16, 2023, Tom Lane <tgl@sss.pgh.pa.us> wrote:

That line of argument also leads to the conclusion that it'd be
okay to expose info about the ordering of the CTE result to the
upper planner.  This patch doesn't do that, and I'm not sufficiently
excited about the issue to go write some code.  But if someone else
does, I think we shouldn't exclude doing it on the grounds of wanting
to preserve an optimization fence.  The fence is sort of one-way
in this line of thinking: information can propagate up to the outer
planner level, but not down into the CTE plan.

This is indeed my understanding of what materialized means.  Basically, the CTE is done first and in isolation; but any knowledge of its result shape can be used when referencing it.

David J.

pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: Wrong rows estimations with joins of CTEs slows queries by more than factor 500
Next
From: Laurenz Albe
Date:
Subject: Re: Wrong rows estimations with joins of CTEs slows queries by more than factor 500