Re: Reference to - BUG #18349: ERROR: invalid DSA memory alloc request size 1811939328, CONTEXT: parallel worker - Mailing list pgsql-bugs

From Andrei Lepikhov
Subject Re: Reference to - BUG #18349: ERROR: invalid DSA memory alloc request size 1811939328, CONTEXT: parallel worker
Date
Msg-id 0c3b0e1b-55d1-42b6-8c3c-4392479187db@gmail.com
Whole thread Raw
In response to Re: Reference to - BUG #18349: ERROR: invalid DSA memory alloc request size 1811939328, CONTEXT: parallel worker  (Craig Milhiser <craig@milhiser.com>)
Responses Re: Reference to - BUG #18349: ERROR: invalid DSA memory alloc request size 1811939328, CONTEXT: parallel worker
List pgsql-bugs
On 10/7/24 18:42, Craig Milhiser wrote:
> 
>     On Oct 1, 2024 Andrei Lepikhov wrote
> 
>  > Can you provide an explain of this query?
> 
> Apologies for the delay. I have been travelling since Wednesday night. 
> Thanks for your help and time with this issue.
> 
> Below is the query, with specific values redacted. An explain with 
> max_parallel_workers_per_gather = 2 and explain analyze 
> max_parallel_workers_per_gather = 0.
I'm a bit confused: the thread subject named ' invalid DSA memory alloc 
request size ...', but you write about issue with OOM killer. It is two 
different issues, which one do you have exactly?

OOM killer can be explained easily, because I see huge string_agg 
aggregate - workers can utilise memory more intensively. For now, 
explain of an Aggregate node don't show information about factual sort 
operation of each aggregate and memory consumption.

-- 
regards, Andrei Lepikhov




pgsql-bugs by date:

Previous
From: Cassandra Thrift
Date:
Subject: pg_dump throwing segfault error during backup
Next
From: Amit Kapila
Date:
Subject: Re: BUG #18644: ALTER PUBLICATION ... SET (publish_via_partition_root) wrong/undocumented behavior.