From: Andrei Lepikhov <a.lepikhov@postgrespro.ru>
To: alexey.ermakov@dataegret.com, pgsql-bugs@lists.postgresql.org, PG Bug reporting form <noreply@postgresql.org>
Subject: Re: BUG #18349: ERROR: invalid DSA memory alloc request size 1811939328, CONTEXT: parallel worker
Date: Fri, 16 Feb 2024 21:40:03 +0700
Message-ID: <512ef568-336e-4087-ba23-f22b006d329d@postgrespro.ru> (raw)
In-Reply-To: <18349-83d33dd3d0c855c3@postgresql.org>
References: <18349-83d33dd3d0c855c3@postgresql.org>
On 16/2/2024 20:18, PG Bug reporting form wrote:
> Interesting thing: after query fails it take some time (seconds) before psql
> gives control back.
> It turns out that postgresql written 1M+ (!) temporary files (most of them
> are empty) and cleaning up takes some time.
Interesting. It correlates with one performance issue I have been trying
to catch already 3 months. Could you provide some reproduction of that
behavior?
> With bigger work_mem it won't write so many files. Maybe memory issue
> somehow related with number of files.
>
> In PostgreSQL 16.2 there were fix for similar bug: [1],[2]. Could it be that
> there is some issue with it ?
Looks like surely the same issue we fixed recently: Parallel Hash Join +
DSM is a sign of that problem.
--
regards,
Andrei Lepikhov
Postgres Professional
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: a.lepikhov@postgrespro.ru, noreply@postgresql.org
Subject: Re: BUG #18349: ERROR: invalid DSA memory alloc request size 1811939328, CONTEXT: parallel worker
In-Reply-To: <512ef568-336e-4087-ba23-f22b006d329d@postgrespro.ru>
* 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