Re: Implement missing join selectivity estimation for range types

SCHOEMANS Maxime <maxime.schoemans@ulb.be>

From: SCHOEMANS Maxime <maxime.schoemans@ulb.be>

To: Haibo Yan <tristan.yim@gmail.com>

Cc: vignesh C <vignesh21@gmail.com>, Tom Lane <tgl@sss.pgh.pa.us>, Damir Belyalov <dam.bel07@gmail.com>, jian he <jian.universality@gmail.com>, PostgreSQL Hackers <pgsql-hackers@lists.postgresql.org>, SAKR Mahmoud <mahmoud.sakr@ulb.be>, Diogo Repas <diogo.repas@gmail.com>, Andrey Lepikhov <a.lepikhov@postgrespro.ru>

Date: 2026-04-21T13:54:33Z

Lists: pgsql-hackers

Attachments

v8-0001-Improve-range-join-selectivity-estimation-for.patch (application/octet-stream) patch v8-0001
v8-0002-Improve-multirange-join-selectivity-estimation-fo.patch (application/octet-stream) patch v8-0002
v8-0003-Remove-duplicate-selectivity-functions-between-ra.patch (application/octet-stream) patch v8-0003

Hi Haibo,

Thanks for the continued feedback. Attached is v8 addressing your nits
on patch 2:

- Reworded the commit message to say "the same outer-bounds-based
  estimator can be reused" instead of implying the code is just
  duplicated.
- Made comments in multirangejoinsel type-neutral where they
  unnecessarily said "range" (e.g. "bound histograms" instead of
  "range histograms", "empty values" instead of "empty ranges").
- Added the reverse mixed-direction tests (multirange x range).

Regards,
Maxime