| From: | Justin Pryzby <pryzby(at)telsasoft(dot)com> |
|---|---|
| To: | pgsql-hackers(at)lists(dot)postgresql(dot)org |
| Cc: | Jeff Janes <jeff(dot)janes(at)gmail(dot)com> |
| Subject: | explain HashAggregate to report bucket and memory stats |
| Date: | 2020-01-03 16:19:26 |
| Message-ID: | 20200103161925.GM12066@telsasoft.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Sun, Feb 17, 2019 at 11:29:56AM -0500, Jeff Janes wrote:
https://www.postgresql.org/message-id/CAMkU%3D1zBJNVo2DGYBgLJqpu8fyjCE_ys%2Bmsr6pOEoiwA7y5jrA%40mail.gmail.com
> What would I find very useful is [...] if the HashAggregate node under
> "explain analyze" would report memory and bucket stats; and if the Aggregate
> node would report...anything.
Find attached my WIP attempt to implement this.
Jeff: can you suggest what details Aggregate should show ?
Justin
| Attachment | Content-Type | Size |
|---|---|---|
| v1-0001-refactor-show_hinstrument-and-avoid-showing-memor.patch | text/x-diff | 4.0 KB |
| v1-0002-explain-analyze-to-show-stats-from-hash-aggregate.patch | text/x-diff | 8.3 KB |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Robert Haas | 2020-01-03 16:24:32 | Re: Greatest Common Divisor |
| Previous Message | Justin Pryzby | 2020-01-03 16:03:15 | Re: distinguish index cost component from table component |