Re: Fwd: pg18 bug? SELECT query doesn't work

From: Richard Guo <guofenglinux(at)gmail(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Eric Ridge <eebbrr(at)gmail(dot)com>, Pg Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>
Subject: Re: Fwd: pg18 bug? SELECT query doesn't work
Date: 2026-01-16 03:27:36
Message-ID: CAMbWs48NWyUvS3LPW6xVsxeZy+23CK3Jk4MMoc-k+Tj1tNLHmQ@mail.gmail.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-general pgsql-hackers

On Fri, Jan 9, 2026 at 6:52 PM Richard Guo <guofenglinux(at)gmail(dot)com> wrote:
> 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().

I plan to push and backpatch this patch early next week, barring any
objections.

- Richard

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2026-01-16 03:37:28 Re: Remove no-op PlaceHolderVars
Previous Message Michael Paquier 2026-01-16 03:19:01 Re: fix a spelling mistake

Browse pgsql-general by date

  From Date Subject
Previous Message Adrian Klaver 2026-01-15 19:24:33 Re: How did VACUUM ANALYZE reclaim large TOAST bloat at disk level in PostgreSQL 16?