ov 17, 2021 at 7:47 PM Tomas Vondra
wrote:
> On 11/17/21 16:39, Xiaozhe Yao wrote:
> > Hi Tom,
> >
> > Thanks for your feedback. I completely agree with you that a
> > higher-level hook is better suited for this case. I have adjusted the
> > PoC pa
Hi Tom,
Thanks for your feedback. I completely agree with you that a higher-level
hook is better suited for this case. I have adjusted the PoC patch to this
email.
Now it is located in the clauselist_selectivity_ext function, where we
first check if the hook is defined. If so, we let the hook
t regards,
Xiaozhe
On Wed, Nov 17, 2021 at 2:49 PM Tomas Vondra
wrote:
>
>
> On 11/17/21 2:24 PM, Xiaozhe Yao wrote:
> > Hi hackers,
> >
> > I am currently working on improving the cardinality estimation component
> > in PostgreSQL with machine learning. I came up w
Hi hackers,
I am currently working on improving the cardinality estimation component in
PostgreSQL with machine learning. I came up with a solution that mutates
the bounds for different columns. For example, assume that we have a query
```
select * from test where X<10 and Y<20;
```
Our
