Re: Implement missing join selectivity estimation for range types

From: Tomas Vondra <tomas(dot)vondra(at)enterprisedb(dot)com>
To: Mahmoud Sakr <mahmoud(dot)sakr(at)ulb(dot)be>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>
Cc: SCHOEMANS Maxime <Maxime(dot)Schoemans(at)ulb(dot)be>, Diogo Repas <diogo(dot)repas(at)gmail(dot)com>, Luo Zhicheng <zhicheng(dot)luo(at)ulb(dot)be>, Andrey Lepikhov <a(dot)lepikhov(at)postgrespro(dot)ru>
Subject: Re: Implement missing join selectivity estimation for range types
Date: 2023-01-18 18:07:23
Message-ID: 1bc5e1e4-380b-213d-6e6a-d5e8f7f0c7f5@enterprisedb.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Also, calc_hist_selectivity_contains in multirangetypes_selfuncs.c needs
a proper comment, not just "this is a copy from rangetypes".

However, it seems the two functions are exactly the same. Would the
functions diverge in the future? If not, maybe there should be just a
single shared function?

regards

--
Tomas Vondra
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Bruce Momjian 2023-01-18 18:11:12 Re: document the need to analyze partitioned tables
Previous Message Justin Pryzby 2023-01-18 17:49:19 Re: document the need to analyze partitioned tables