Re: Propose a new hook for mutating the query bounds - Mailing list pgsql-hackers

From Xiaozhe Yao
Subject Re: Propose a new hook for mutating the query bounds
Date
Msg-id CAAxqZp_NH+aHQ6hO2PwrJSZb=9arPZDt5fueTrHiXASCh0623A@mail.gmail.com
Whole thread Raw
In response to Re: Propose a new hook for mutating the query bounds  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: Propose a new hook for mutating the query bounds
List pgsql-hackers
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 estimate the selectivity and return the result. With this one, I can also develop extensions to better estimate the selectivity.

I hope it makes more sense. Also please forgive me if I am understanding Postgres somehow wrong, as I am quite new to this community :)

Best regards,
Xiaozhe
Attachment

pgsql-hackers by date:

Previous
From: Dmitry Dolgov
Date:
Subject: Re: Keep notnullattrs in RelOptInfo (Was part of UniqueKey patch series)
Next
From: Mark Dilger
Date:
Subject: Re: Non-superuser subscription owners