| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com> |
| Cc: | Benoit Ryder <b(dot)ryder(at)ateme(dot)com>, "pgsql-bugs(at)lists(dot)postgresql(dot)org" <pgsql-bugs(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: BUG #18429: Inconsistent results on similar queries with join lateral |
| Date: | 2024-04-12 19:01:50 |
| Message-ID: | 481322.1712948510@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
"David G. Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com> writes:
> On Fri, Apr 12, 2024 at 8:50 AM Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
>> I'm not seeing a bulletproof way offhand, other than "update to v16".
> Q1 is trivially fixed by specifying "WITH c2 AS MATERIALIZED ( ... )", No?
Q1 as stated, yeah. But the question was about generically avoiding
this bug, and I'm not yet sure about how to do that in cases not
involving a WITH boundary (eg Q3,Q4).
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2024-04-12 19:14:15 | Re: BUG #18430: syntax error when using aggregate function in where clause of subquery |
| Previous Message | David G. Johnston | 2024-04-12 18:59:30 | Re: BUG #18430: syntax error when using aggregate function in where clause of subquery |