| From: | Andrei Lepikhov <lepihov(at)gmail(dot)com> |
|---|---|
| To: | pgsql-hackers(at)lists(dot)postgresql(dot)org |
| Cc: | Alexander Korotkov <aekorotkov(at)gmail(dot)com>, Zsolt Parragi <zsolt(dot)parragi(at)percona(dot)com> |
| Subject: | Re: Propagate LIMIT bound through the outer side of left join |
| Date: | 2026-11-03 07:54:20 |
| Message-ID: | 1c0860b6-a1f8-40ed-867b-0ddad458d095@gmail.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Here is a new version of the feature.
HashJoin in multi-batch mode doesn't satisfy the key contract not to pull more
tuples than necessary. Hence, I removed it from the optimisation.
Also, some cleanup in code comments and test improvements are included.
--
regards, Andrei Lepikhov,
pgEdge
| Attachment | Content-Type | Size |
|---|---|---|
| v3-0001-Propagate-LIMIT-bound-through-the-outer-side-of-l.patch | text/plain | 17.6 KB |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Chao Li | 2026-11-03 07:59:42 | Re: Assertion failure when importing expression statistics with nested JSON values |
| Previous Message | Zhijie Hou | 2026-11-03 07:43:57 | Re: Proposal: Conflict log history table for Logical Replication |