From: Tom Lane <tgl@sss.pgh.pa.us>
To: Nathaniel Hazelton <nathaniel@sturdyai.com>
cc: "pgsql-bugs@lists.postgresql.org" <pgsql-bugs@lists.postgresql.org>
Subject: Re: BUG #17721: A completely unused CTE negatively affect Query Plan
In-reply-to: <BD7EBA1F-4FB7-43CC-A70B-42439454EAE5@sturdyai.com>
References: <17721-a660b93948b165a7@postgresql.org>
 <2784036.1671042328@sss.pgh.pa.us>
 <BD7EBA1F-4FB7-43CC-A70B-42439454EAE5@sturdyai.com>
Comments: In-reply-to Nathaniel Hazelton <nathaniel@sturdyai.com>
	message dated "Wed, 14 Dec 2022 22:14:07 +0000"
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-ID: <2998992.1671058060.1@sss.pgh.pa.us>
Date: Wed, 14 Dec 2022 17:47:40 -0500
Message-ID: <2998993.1671058060@sss.pgh.pa.us>
Archived-At: 
 <https://www.postgresql.org/message-id/2998993.1671058060%40sss.pgh.pa.us>
Precedence: bulk

Nathaniel Hazelton <nathaniel@sturdyai.com> writes:
> The CTE in that location was emulating a view in which we have a CTE -
> which responds the same way.  Does this mean CTEs can never be used in
> views that could be flattened without affecting performance?

You've got a view with an unused CTE?  Why?

But at any rate, yes, the presence of a CTE is an optimization
fence: we can't flatten the subquery containing it without losing
the query level at which the CTE should be evaluated.  Perhaps there
are special cases where that could be relaxed, but nobody's tried
very hard.

			regards, tom lane