From: Eric Ridge <eebbrr@gmail.com>
Message-Id: <11E075EF-20F5-42CD-A014-16172FF05CCF@gmail.com>
Content-Type: multipart/alternative;
	boundary="Apple-Mail=_AFE8688D-CD12-4108-8E0B-EB7E2EDF9C9C"
Mime-Version: 1.0 (Mac OS X Mail 16.0 \(3826.500.181.1.5\))
Subject: Re: pg18 bug? SELECT query doesn't work
Date: Tue, 6 Jan 2026 11:16:08 -0500
In-Reply-To: <CAKFQuwbQj6kLxiz=Ft=ykM2s+H0ytCL7C+Cg1G=7W8ifhFi0Ow@mail.gmail.com>
Cc: pgsql-general <pgsql-general@postgresql.org>
To: "David G. Johnston" <david.g.johnston@gmail.com>
References: <7900964C-F99E-481E-BEE5-4338774CEB9F@gmail.com>
 <CAKFQuwbQj6kLxiz=Ft=ykM2s+H0ytCL7C+Cg1G=7W8ifhFi0Ow@mail.gmail.com>
Archived-At: <https://www.postgresql.org/message-id/11E075EF-20F5-42CD-A014-16172FF05CCF%40gmail.com>
Precedence: bulk


--Apple-Mail=_AFE8688D-CD12-4108-8E0B-EB7E2EDF9C9C
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=utf-8

> On Jan 6, 2026, at 11:04=E2=80=AFAM, David G. Johnston =
<david.g.johnston@gmail.com> wrote:
>=20
>=20
> It was an intentional change.  You now should be putting set-producing =
functions into the FROM clause of a query or subquery.  A lateral join =
is often required.

I'm willing to accept that, but I can't find this called out in the =
release notes between 15 and 18.1.  I could have overlooked it, of =
course.

It is very surprising to me that Postgres would intentionally break =
previously-working SELECT statements and that the CTE version is =
inconsistent between "AS MATERIALIZED".  The WITH MATERIALIZED docs =
don't mention anything about certain query shapes being incompatible.

eric


--Apple-Mail=_AFE8688D-CD12-4108-8E0B-EB7E2EDF9C9C
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html;
	charset=utf-8

<html><head><meta http-equiv=3D"content-type" content=3D"text/html; =
charset=3Dutf-8"></head><body style=3D"overflow-wrap: break-word; =
-webkit-nbsp-mode: space; line-break: =
after-white-space;"><div><blockquote type=3D"cite"><div>On Jan 6, 2026, =
at 11:04=E2=80=AFAM, David G. Johnston =
&lt;david.g.johnston@gmail.com&gt; wrote:</div><br =
class=3D"Apple-interchange-newline"><div><div dir=3D"ltr"><div =
dir=3D"ltr"><div class=3D"gmail_default" =
style=3D"font-family:arial,helvetica,sans-serif"><br></div></div><div =
class=3D"gmail_quote gmail_quote_container"><div class=3D"gmail_default" =
style=3D"font-family:arial,helvetica,sans-serif">It was an =
intentional&nbsp;change.&nbsp; You now should be putting set-producing =
functions into the FROM clause of a query or subquery.&nbsp; A lateral =
join is often =
required.</div></div></div></div></blockquote><div><br></div>I'm willing =
to accept that, but I can't find this called out in the release notes =
between 15 and 18.1. &nbsp;I could have overlooked it, of =
course.</div><div><br></div><div>It is very surprising to me that =
Postgres would intentionally break previously-working SELECT statements =
and that the CTE version is inconsistent between "AS MATERIALIZED". =
&nbsp;The WITH MATERIALIZED docs don't mention anything about certain =
query shapes being =
incompatible.</div><div><br></div><div>eric</div><div><br></div><br></body=
></html>=

--Apple-Mail=_AFE8688D-CD12-4108-8E0B-EB7E2EDF9C9C--