| From: | solaimurugan vellaipandiyan <drsolaimurugan(dot)v(at)gmail(dot)com> |
|---|---|
| To: | Petr Petrov <p(dot)petrov(at)postgrespro(dot)ru> |
| Cc: | Alena Rybakina <a(dot)rybakina(at)postgrespro(dot)ru>, Ilia Evdokimov <ilya(dot)evdokimov(at)tantorlabs(dot)com>, David Rowley <dgrowleyml(at)gmail(dot)com>, Ranier Vilela <ranier(dot)vf(at)gmail(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: pull-up subquery if JOIN-ON contains refs to upper-query |
| Date: | 2026-05-11 05:20:20 |
| Message-ID: | CAHEL7KTFh+W6HSEETpv_=P8weLKNrWPAu6y6GLwrKhnhENOTWg@mail.gmail.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Hi Alena,
I did some additional testing on the latest patch and the behavior
looks good in my environment so far.
I verified the original EXISTS pull-up case and confirmed that after
applying the patch the planner generates optimized Semi Join plans
instead of EXISTS(SubPlan).
I also tested several additional cases discussed in the thread, including:
1.NOT EXISTS queries
2. constant qual conditions
3. ANY array conditions
4. LEFT JOIN cases
5. FULL JOIN cases
For the FULL JOIN scenarios, I checked both the execution plans and
actual query results. In one case the planner simplified the query
into a Hash Join plan, but the final query results remained correct.
I additionally ran:
- make check
- make -C contrib check
Both completed successfully in my environment and I did not observe
planner crashes or incorrect query results during testing.
Overall, the patch seems to improve planner behavior consistently for
these EXISTS pull-up scenarios.
Regards,
Solaimurugan V
| From | Date | Subject | |
|---|---|---|---|
| Next Message | JoongHyuk Shin | 2026-05-11 05:27:58 | Are extended statistics intentionally not propagated to partitions? |
| Previous Message | Tom Lane | 2026-05-11 05:04:54 | Re: Review - Patch for pg_bsd_indent: improve formatting of multiline comments |