| From: | David Rowley <dgrowleyml(at)gmail(dot)com> |
|---|---|
| To: | Tomas Vondra <tomas(dot)vondra(at)enterprisedb(dot)com> |
| Cc: | Dilip Kumar <dilipbalaut(at)gmail(dot)com>, David Geier <geidav(dot)pg(at)gmail(dot)com>, PostgreSQL Developers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: Parallel Bitmap Heap Scan reports per-worker stats in EXPLAIN ANALYZE |
| Date: | 2024-07-09 02:44:23 |
| Message-ID: | CAApHDvpy2y-WX_2_E3HTAg8b=gOGzUQBYHxfXzqVwEMhKQTTDQ@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Tue, 9 Jul 2024 at 11:51, David Rowley <dgrowleyml(at)gmail(dot)com> wrote:
> I think we should consider aligning Parallel Hash
> with the other Parallel node behaviour.
I looked at that and quickly realised that it makes sense that
Parallel Hash does something different here. All the workers are
contributing to building the same hash table, so they're all going to
show the same set of values, provided they managed to help building
it.
We're able to tell how much each worker helped according to EXPLAIN
(ANALYZE, VERBOSE)'s Worker N: rows=n output. I don't think there's
anything else not already shown that would be interesting to know per
worker.
David
| From | Date | Subject | |
|---|---|---|---|
| Next Message | David Rowley | 2024-07-09 02:49:41 | Re: Add memory/disk usage for WindowAgg nodes in EXPLAIN |
| Previous Message | Tatsuo Ishii | 2024-07-09 02:44:12 | Re: Add memory/disk usage for WindowAgg nodes in EXPLAIN |