| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Jeff Janes <jeff(dot)janes(at)gmail(dot)com> |
| Cc: | Donald Dong <xdong(at)csumb(dot)edu>, Tomas Vondra <tomas(dot)vondra(at)2ndquadrant(dot)com>, David Fetter <david(at)fetter(dot)org>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: Actual Cost |
| Date: | 2019-02-17 18:56:23 |
| Message-ID: | 31101.1550429783@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Jeff Janes <jeff(dot)janes(at)gmail(dot)com> writes:
> What would I find very useful is a verbosity option to get the cost
> estimates expressed as a multiplier of each *_cost parameter, rather than
> just as a scalar.
Perhaps, but refactoring to get that seems impractically invasive &
expensive, since e.g. index AM cost estimate functions would have to
be redefined, plus we'd have to carry around some kind of cost vector
rather than single numbers for every Path ...
> And at the whole-query level, get an rusage report
> rather than just wall-clock duration.
I'm sure you're aware of log_statement_stats and friends already.
I agree though that that's not necessarily an optimal user interface.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Donald Dong | 2019-02-17 19:05:39 | Re: Actual Cost |
| Previous Message | Michael Banck | 2019-02-17 18:31:38 | Re: Offline enabling/disabling of data checksums |