| From: | Jeff Davis <pgsql(at)j-davis(dot)com> |
|---|---|
| To: | David Rowley <dgrowleyml(at)gmail(dot)com>, PostgreSQL Developers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: Missing HashAgg EXPLAIN ANALYZE details for parallel plans |
| Date: | 2020-06-19 03:28:30 |
| Message-ID: | 258e053f0c555b01912f2c48c2ade9f7295a3604.camel@j-davis.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Thu, 2020-06-18 at 15:37 +1200, David Rowley wrote:
> The attached patch fixes both the missing parallel worker information
> and puts the properties on a single line for format=text.
Thank you.
I noticed some strange results in one case where one worker had a lot
more batches than another. After I investigated, I think everything is
fine -- it seems that one worker was getting more tuples from the
underlying parallel scan. So everything looks good to me.
Regards,
Jeff Davis
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Amit Kapila | 2020-06-19 03:29:48 | Re: min_safe_lsn column in pg_replication_slots view |
| Previous Message | Kyotaro Horiguchi | 2020-06-19 03:13:56 | Re: min_safe_lsn column in pg_replication_slots view |