Re: [HACKERS] [PATCH] Overestimated filter cost and its mitigation

2018-01-16 Thread Yuto Hayamizu
could review other's patches. One patch reviewed for one patch > > submitted, with equal difficulty. You should also get a community > > account so as it is possible to add your name as an author of this > > patch. > > While this patch does still apply, it doesn't

Re: [HACKERS] [PATCH] Overestimated filter cost and its mitigation

2018-01-19 Thread Yuto Hayamizu
On Wed, Nov 8, 2017 at 6:48 AM, Tom Lane wrote: > Because (1) up to now there's been no need to consider the qual ordering > till later, and (2) re-doing that sort for each path seemed unduly > expensive. If we're to try to estimate whether later quals will be > reached, then sure the ordering be

Re: [HACKERS] [PATCH] Overestimated filter cost and its mitigation

2018-01-19 Thread Yuto Hayamizu
the order in the larger set, which I guess is true > about all separator functions. For this patch, sorting of a qual list happens only once for each range table entry, not for each path. So there is no need for caching sorted qual lists as far as I know. ---- regards, Yuto Hayamizu

Re: [HACKERS] [PATCH] Overestimated filter cost and its mitigation

2018-01-28 Thread Yuto Hayamizu
On Fri, Jan 19, 2018 at 5:07 PM, Yuto Hayamizu wrote: > My idea of improving this patch is that give a threshold N_limit, > and for q_1 ... q_N_limit, do the same weighted cost estimation in the > current version of this patch. > For q_{N_limit+1} , stop calling clauselist_sel