Re: Fwd: pg18 bug? SELECT query doesn't work
Richard Guo <guofenglinux@gmail.com>
From: Richard Guo <guofenglinux@gmail.com>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: Eric Ridge <eebbrr@gmail.com>,
Pg Hackers <pgsql-hackers@lists.postgresql.org>
Date: 2026-01-09T09:52:00Z
Lists: pgsql-hackers, pgsql-general
Attachments
- v1-0001-Fix-unsafe-pushdown-of-quals-referencing-grouping.patch (application/octet-stream) patch v1-0001
On Thu, Jan 8, 2026 at 10:30 PM Richard Guo <guofenglinux@gmail.com> wrote: > How about we add a comment to check_output_expressions() along the > below lines? I've worked on the comment a bit more in the attached patch, which also includes my previously proposed code changes and some test cases. I think this patch is suitable for fixing the current bug in the back branches. We can use a separate patch for the more ambitious goal of moving the push-down of subquery's restriction clauses into subquery_planner(). Any thoughts? - Richard
Commits
Same data as JSON:
GET /api/v1/messages/:b64id/commits
the thread's linked commits as JSON, with link sources.
API reference →
-
Fix unsafe pushdown of quals referencing grouping Vars
- 7650eabb662f 18.2 landed
- 34740b90bc12 19 (unreleased) landed
-
Introduce an RTE for the grouping step
- 247dea89f761 18.0 cited