| From: | David Rowley <dgrowleyml(at)gmail(dot)com> |
|---|---|
| To: | Justin Pryzby <pryzby(at)telsasoft(dot)com> |
| Cc: | PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>, Jeff Davis <jdavis(at)postgresql(dot)org> |
| Subject: | Re: pg13dev: explain partial, parallel hashagg, and memory use |
| Date: | 2020-08-06 12:44:19 |
| Message-ID: | CAApHDvpgNLjSv1oB_-9bPfBKDTUgMdycBMp-FdYcF6P+icbgJg@mail.gmail.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Wed, 5 Aug 2020 at 17:25, David Rowley <dgrowleyml(at)gmail(dot)com> wrote:
>
> On Wed, 5 Aug 2020 at 14:27, David Rowley <dgrowleyml(at)gmail(dot)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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | James Coleman | 2020-08-06 13:14:12 | Any objection to documenting pg_sequence_last_value()? |
| Previous Message | David Rowley | 2020-08-06 12:41:04 | Re: Hybrid Hash/Nested Loop joins and caching results from subplans |