From: Tom Lane <tgl@sss.pgh.pa.us>
To: kamil@monicz.dev
cc: pgsql-bugs@lists.postgresql.org
Subject: Re: BUG #19106: Potential regression with CTE materialization
 planning in Postgres 18
In-reply-to: <19106-9dd3668a0734cd72@postgresql.org>
References: <19106-9dd3668a0734cd72@postgresql.org>
Comments: In-reply-to PG Bug reporting form <noreply@postgresql.org>
	message dated "Sun, 09 Nov 2025 13:52:01 +0000"
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-ID: <1650411.1762703636.1@sss.pgh.pa.us>
Content-Transfer-Encoding: quoted-printable
Date: Sun, 09 Nov 2025 10:53:56 -0500
Message-ID: <1650412.1762703636@sss.pgh.pa.us>
Archived-At: 
 <https://www.postgresql.org/message-id/1650412.1762703636%40sss.pgh.pa.us>
Precedence: bulk

PG Bug reporting form <noreply@postgresql.org> writes:
> After upgrading from Postgres 17 to 18, one of my queries started raisin=
g an
> error:
> "unexpected outer reference in CTE query"

I agree that sounds like a bug ...

> The problematic query is:
> https://github.com/openstreetmap-ng/openstreetmap-ng/blob/eb805d8766fb4b=
359b96eb6b50acc8c2a835a165/app/services/element_spatial_service.py#L82-L21=
5

... but I am not going to spend time trying to reproduce it given
this amount of detail.  There's too much missing context, like what
data you were running the query on.  I could spend all day, not
see the failure, and be left no wiser than before as to whether
it's already fixed or I just didn't duplicate your context closely
enough.  Please see if you can reduce the problem case to a
self-contained SQL script.

			regards, tom lane