| From: | Ilia Evdokimov <ilya(dot)evdokimov(at)tantorlabs(dot)com> |
|---|---|
| To: | prankware <esavelievcode(at)gmail(dot)com>, Osama Abdul Qader <osamaabdulqader(dot)cs(at)gmail(dot)com>, pgsql-hackers(at)lists(dot)postgresql(dot)org |
| Cc: | Laurenz Albe <laurenz(dot)albe(at)cybertec(dot)at> |
| Subject: | Re: COALESCE patch |
| Date: | 2026-09-23 04:35:21 |
| Message-ID: | 1c16fa71-2487-4653-8f10-6478cde336ec@tantorlabs.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
While reviewing v6, I noticed try_coalesce_eq() in eqjoinsel() returns
before the function ever looks at sjinfo->jointype, so SEMI/ANTI joins
get the same formula meant for INNER/LEFT/FULL. I'm not sure it is true.
Shouldn't the fat path be restricted to INNER/LEFT/FULL until SEMI/ANTI
get their own existence-base treatment?
--
Best regards,
Ilia Evdokimov,
Tantor Labs LLC,
https://tantorlabs.com/
| From | Date | Subject | |
|---|---|---|---|
| Next Message | shveta malik | 2026-09-23 04:35:27 | Re: sequencesync worker race with REFRESH SEQUENCES |
| Previous Message | Masahiko Sawada | 2026-09-23 04:19:58 | Re: Adding a range check on the sequence index from the publisher. |