| From: | Eric Ridge <eebbrr(at)gmail(dot)com> |
|---|---|
| To: | "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com> |
| Cc: | pgsql-general <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: pg18 bug? SELECT query doesn't work |
| Date: | 2026-01-06 16:16:08 |
| Message-ID: | 11E075EF-20F5-42CD-A014-16172FF05CCF@gmail.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general pgsql-hackers |
> On Jan 6, 2026, at 11:04 AM, David G. Johnston <david(dot)g(dot)johnston(at)gmail(dot)com> wrote:
>
>
> 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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | David G. Johnston | 2026-01-06 17:00:29 | Re: pg18 bug? SELECT query doesn't work |
| Previous Message | David G. Johnston | 2026-01-06 16:04:01 | Re: pg18 bug? SELECT query doesn't work |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Jacob Champion | 2026-01-06 16:17:04 | Re: Proposal to allow setting cursor options on Portals |
| Previous Message | David G. Johnston | 2026-01-06 16:04:01 | Re: pg18 bug? SELECT query doesn't work |