public inbox for [email protected]
help / color / mirror / Atom feedFrom: solaimurugan vellaipandiyan <[email protected]>
To: Petr Petrov <[email protected]>
Cc: Alena Rybakina <[email protected]>
Cc: Ilia Evdokimov <[email protected]>
Cc: David Rowley <[email protected]>
Cc: Ranier Vilela <[email protected]>
Cc: PostgreSQL Hackers <[email protected]>
Subject: Re: pull-up subquery if JOIN-ON contains refs to upper-query
Date: Mon, 11 May 2026 10:50:20 +0530
Message-ID: <CAHEL7KTFh+W6HSEETpv_=P8weLKNrWPAu6y6GLwrKhnhENOTWg@mail.gmail.com> (raw)
In-Reply-To: <[email protected]>
References: <[email protected]>
<CAEudQAoD707uh5Pjpg5NMyF-QO=fzajA+BmtcoqQAeXN1C+TkQ@mail.gmail.com>
<[email protected]>
<[email protected]>
<[email protected]>
<[email protected]>
<[email protected]>
<[email protected]>
<[email protected]>
<[email protected]>
<[email protected]>
<[email protected]>
<[email protected]>
<[email protected]>
<[email protected]>
<CAHEL7KS2euWWoXYUL_NnaFc5j7QggobmfYFWDm-eTJFYONdRQA@mail.gmail.com>
<[email protected]>
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
view thread (22+ messages) latest in thread
reply
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: [email protected]
Cc: [email protected], [email protected], [email protected], [email protected], [email protected], [email protected], [email protected]
Subject: Re: pull-up subquery if JOIN-ON contains refs to upper-query
In-Reply-To: <CAHEL7KTFh+W6HSEETpv_=P8weLKNrWPAu6y6GLwrKhnhENOTWg@mail.gmail.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox