On Sat, Feb 16, 2019 at 03:10:44PM -0800, Donald Dong wrote:
> Hi,
>
> When explaining a query, I think knowing the actual rows and pages
> in addition to the operation type (e.g seqscan) would be enough to
> calculate the actual cost. The actual cost metric could be useful
> when we want to look into how off is the planner's estimation, and
> the correlation between time and cost. Would it be a feature worth
> considering?
As someone not volunteering to do any of the work, I think it'd be a
nice thing to have. How large an effort would you guess it would be
to build a proof of concept?
Best,
David.
--
David Fetter <david(at)fetter(dot)org> http://fetter.org/
Phone: +1 415 235 3778
Remember to vote!
Consider donating to Postgres: http://www.postgresql.org/about/donate