Re: Implement missing join selectivity estimation for range types

From: Alena Rybakina <lena(dot)ribackina(at)yandex(dot)ru>
To: Schoemans Maxime <maxime(dot)schoemans(at)ulb(dot)be>
Cc: Damir Belyalov <dam(dot)bel07(at)gmail(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>, SAKR Mahmoud <mahmoud(dot)sakr(at)ulb(dot)be>, Diogo Repas <diogo(dot)repas(at)gmail(dot)com>, LUO Zhicheng <zhicheng(dot)luo(at)ulb(dot)be>, Tomas Vondra <tomas(dot)vondra(at)enterprisedb(dot)com>, Andrey Lepikhov <a(dot)lepikhov(at)postgrespro(dot)ru>
Subject: Re: Implement missing join selectivity estimation for range types
Date: 2023-11-30 14:50:36
Views: Raw Message | Whole Thread | Download mbox | Resend email
Lists: pgsql-hackers


Thank you for your work on the subject, I think it's a really useful
feature and it allows optimizer to estimate more correctly clauses with
such type of operator.

I rewieved your patch and noticed that some comments are repeated into
multirangejoinsel functions, I suggest combining them.

The proposed changes are in the attached patch.

If this topic is about calculating selectivity, have you thought about
adding cardinality calculation test for queries with this type of operator?

For example, you could form queries similar to those that you use in
src/test/regress/sql/multirangetypes.sql and

I added a few in the attached patch.

Alena Rybakina

Attachment Content-Type Size
changes.diff.txt text/plain 10.4 KB

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Konstantin Knizhnik 2023-11-30 15:40:15 Re: Custom explain options
Previous Message Robert Haas 2023-11-30 14:33:04 Re: trying again to get incremental backup