pg.ddx.io  pgsql-bugs@postgresql.org mailing list archive  

help / color / mirror / Atom feed
From: Andrei Lepikhov <lepihov@gmail.com>
To: Craig Milhiser <craig@milhiser.com>
Cc: Thomas Munro <thomas.munro@gmail.com>
Cc: Tom Lane <tgl@sss.pgh.pa.us>
Cc: pgsql-bugs@lists.postgresql.org
Subject: Re: Reference to - BUG #18349: ERROR: invalid DSA memory alloc request size 1811939328, CONTEXT: parallel worker
Date: Tue, 8 Oct 2024 16:16:13 +0700
Message-ID: <0c3b0e1b-55d1-42b6-8c3c-4392479187db@gmail.com> (raw)
In-Reply-To: <CA+wnhO0VdTP9OVdZP9bmkavma2WkE-pYpP1yW8yDwRrJ97j-2g@mail.gmail.com>
References: <CA+wnhO1OfgXbmXgC4fv_uu=OxcDQuHvfoQ4k0DFeB0Qqd-X-rQ@mail.gmail.com>
	<2878480.1727017360@sss.pgh.pa.us>
	<CA+wnhO1zP13p5sn6d-top=-gmCnE+ymYEfkPbN2d=QKWMbp6Sg@mail.gmail.com>
	<CA+hUKGJo9H75w3QoZrZCVm3eGg7ifJ0UvZZMw6bz=HCpwg0gKw@mail.gmail.com>
	<CA+hUKG+YZpOyP-XXT65o9hx=oGF+9-BJzjqzRXcdvWV=ZrJbTA@mail.gmail.com>
	<CA+wnhO2NDZFWB1TrZga-uLzpfSDjKH5Axa2d2+1Q76JSsS7yMg@mail.gmail.com>
	<CA+wnhO0S2kxJ2_M57uJXRocMpcDtz6N4RkP-3Xy=pFs1wp7hmg@mail.gmail.com>
	<CA+hUKGLPKWamfKjtEkPLvRDSeOqoZZ0wDfU65d-hF-1upL8iGw@mail.gmail.com>
	<CA+wnhO3kT7mxbadbteppSZVcs3FRPvGL5xTY2DbrWSGohmhyVw@mail.gmail.com>
	<6785e9e8-4c64-41b0-9e72-c13d1822b599@gmail.com>
	<CA+wnhO0VdTP9OVdZP9bmkavma2WkE-pYpP1yW8yDwRrJ97j-2g@mail.gmail.com>

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






view thread (27+ messages)  latest in thread

Message-ID: <0c3b0e1b-55d1-42b6-8c3c-4392479187db@gmail.com>
Permalink:  ../0c3b0e1b-55d1-42b6-8c3c-4392479187db@gmail.com/
Also on:    postgresql.org/message-id/0c3b0e1b-55d1-42b6-8c3c-4392479187db@gmail.com

 · 

reply
Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: pgsql-bugs@postgresql.org
  Cc: lepihov@gmail.com, craig@milhiser.com, thomas.munro@gmail.com, tgl@sss.pgh.pa.us, pgsql-bugs@lists.postgresql.org
  Subject: Re: Reference to - BUG #18349: ERROR: invalid DSA memory alloc request size 1811939328, CONTEXT: parallel worker
  In-Reply-To: <0c3b0e1b-55d1-42b6-8c3c-4392479187db@gmail.com>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox