Re: Account for cost and selectivity of HAVING quals
Tom Lane <tgl@sss.pgh.pa.us>
From: Tom Lane <tgl@sss.pgh.pa.us>
To: Ashutosh Bapat <ashutosh.bapat@enterprisedb.com>
Cc: pgsql-hackers <pgsql-hackers@postgresql.org>
Date: 2017-11-01T15:11:54Z
Lists: pgsql-hackers
Ashutosh Bapat <ashutosh.bapat@enterprisedb.com> writes: > On Wed, Nov 1, 2017 at 3:15 AM, Tom Lane <tgl@sss.pgh.pa.us> wrote: >> here's a patch to fix the planner so that eval costs and selectivity of >> HAVING quals are factored into the appropriate plan node numbers. >> ... >> + /* Add cost of qual, if any --- but we ignore its selectivity */ > And may be we should try to explain why can we ignore selectivity. > Similarly for the changes in create_minmaxagg_path(). I'm sure you realize that's because the estimate is already just one row ... but sure, we can spell that out. regards, tom lane
Commits
-
Teach planner to account for HAVING quals in aggregation plan nodes.
- 7b6c07547190 11.0 landed