Re: Reference to - BUG #18349: ERROR: invalid DSA memory alloc request size 1811939328, CONTEXT: parallel worker
Andrei Lepikhov <lepihov@gmail.com>
From: Andrei Lepikhov <lepihov@gmail.com>
To: Craig Milhiser <craig@milhiser.com>
Cc: Thomas Munro <thomas.munro@gmail.com>, Tom Lane <tgl@sss.pgh.pa.us>,
pgsql-bugs@lists.postgresql.org
Date: 2024-10-08T09:16:13Z
Lists: 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
Commits
-
Fix extreme skew detection in Parallel Hash Join.
- 98c7c7152d2d 18.0 landed
- 4ac5d33a8b08 17.1 landed
- 53edc948580f 16.5 landed
- 1831545ca186 15.9 landed
- 20d94899414a 14.14 landed
- 45329466fdc9 13.17 landed
- 4fa80a6d7d4b 12.21 landed