Re: Significant performance issues with array_agg() + HashAggregate plans on Postgres 17 - Mailing list pgsql-performance

From Jeff Davis
Subject Re: Significant performance issues with array_agg() + HashAggregate plans on Postgres 17
Date
Msg-id 973a9511ab3c10d77ee46c4b2cd3bc3210a51550.camel@j-davis.com
Whole thread Raw
In response to Re: Significant performance issues with array_agg() + HashAggregate plans on Postgres 17  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-performance
On Fri, 2026-04-03 at 15:56 -0400, Tom Lane wrote:
> Would it make sense to accumulate those values in a separate field
> child_mem_allocated, rather than redefining what mem_allocated
> means?

I think so unless we can't afford the new field for some reason. It
would be convenient to have the single-context-total available when
deleting the context.

I'll try a quick patch. I'll need to be sure that we can properly
decrement the total in all paths.

Regards,
    Jeff Davis




pgsql-performance by date:

Previous
From: Tom Lane
Date:
Subject: Re: Significant performance issues with array_agg() + HashAggregate plans on Postgres 17
Next
From: David Rowley
Date:
Subject: Re: Significant performance issues with array_agg() + HashAggregate plans on Postgres 17