| From: | Andrey Lepikhov <a(dot)lepikhov(at)postgrespro(dot)ru> |
|---|---|
| To: | Richard Guo <guofenglinux(at)gmail(dot)com> |
| Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, PostgreSQL mailing lists <pgsql-bugs(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: Clause accidentally pushed down ( Possible bug in Making Vars outer-join aware) |
| Date: | 2023-04-21 12:11:04 |
| Message-ID: | 29b06792-77f4-9aad-09a0-58e98399448d@postgrespro.ru |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
On 4/21/23 14:34, Richard Guo wrote:
>
> On Thu, Apr 20, 2023 at 1:06 PM Andrey Lepikhov
> <a(dot)lepikhov(at)postgrespro(dot)ru <mailto:a(dot)lepikhov(at)postgrespro(dot)ru>> wrote:
> Are you worried about upper clauses who reference to C vars? In the
> second form when we've formed A/B join, which would have both outer
> joins' relids in its relid set, the upper clause will be able to be
> applied there, and it is the correct join level.
Yes, of course. I thought about the case with INNER JOINs in between,
something like that:
a LEFT JOIN b ON b.x INNER JOIN c ON (b.x=c.x) LEFT JOIN d ON b.x ...
But, it is still a doubt.
>
> BTW, cfbot reminds that a rebase is needed. So re-attach the two
> patches. Now I think it should be in 'Needs review' again in CF. I'll
> go and do the change.
Thanks!
--
Regards
Andrey Lepikhov
Postgres Professional
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2023-04-21 14:09:00 | Re: BUG #17906: Segmentation fault and database crash during procedure call |
| Previous Message | PG Bug reporting form | 2023-04-21 10:19:03 | BUG #17906: Segmentation fault and database crash during procedure call |