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 CAApHDvpgNLjSv1oB_-9bPfBKDTUgMdycBMp-FdYcF6P+icbgJg@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 17:25, David Rowley <dgrowleyml@gmail.com> wrote:
>
> On Wed, 5 Aug 2020 at 14:27, David Rowley <dgrowleyml@gmail.com> wrote:
> > 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.

Just coming back to this. I'd like to push it soon, but it's currently
late here. I'll look at pushing it in my morning in about 8 hours
time.

If anyone has any comments please let me know before then.

David



pgsql-hackers by date:

Previous
From: David Rowley
Date:
Subject: Re: Hybrid Hash/Nested Loop joins and caching results from subplans
Next
From: James Coleman
Date:
Subject: Any objection to documenting pg_sequence_last_value()?