Re: pg13dev: explain partial, parallel hashagg, and memory use - Mailing list pgsql-hackers

From David Rowley
Subject Re: pg13dev: explain partial, parallel hashagg, and memory use
Date
Msg-id CAApHDvq_cw-ZyPBh3N-kO4PDiHxwo-MN4Dt25d477f8HKm3NAg@mail.gmail.com
Whole thread Raw
In response to Re: pg13dev: explain partial, parallel hashagg, and memory use  (David Rowley <dgrowleyml@gmail.com>)
Responses Re: pg13dev: explain partial, parallel hashagg, and memory use  (David Rowley <dgrowleyml@gmail.com>)
List pgsql-hackers
On Wed, 5 Aug 2020 at 14:27, David Rowley <dgrowleyml@gmail.com> wrote:
>
> On Wed, 5 Aug 2020 at 14:13, Justin Pryzby <pryzby@telsasoft.com> wrote:
> > Also odd (to me).  If I encourage more workers, there are "slots" for each
> > "planned" worker, even though fewer were launched:
>
> Looking at explain.c for "num_workers; " (including the final space at
> the end), looking at each for loop that loops over each worker, quite
> a number of those locations have a condition that skips the worker.
>
> For example, show_sort_info() does
>
> if (sinstrument->sortMethod == SORT_TYPE_STILL_IN_PROGRESS)
> continue; /* ignore any unfilled slots */
>
> So maybe Hash Agg should be doing something similar.  Additionally,
> maybe it should not show the leader details if the leader didn't help.

Here's what I had in mind.

The unpatched format got even more broken with EXPLAIN (ANALYZE,
VERBOSE), so this is certainly a bug fix.

David

Attachment

pgsql-hackers by date:

Previous
From: Peter Geoghegan
Date:
Subject: Re: LSM tree for Postgres
Next
From: Kyotaro Horiguchi
Date:
Subject: Re: For standby pg_ctl doesn't wait for PM_STATUS_READY in presence of promote_trigger_file