From: Tom Lane <tgl@sss.pgh.pa.us>
To: Thomas Munro <thomas.munro@gmail.com>
Cc: nageshdbaa@gmail.com
Cc: pgsql-bugs@lists.postgresql.org
Subject: Re: BUG #19105: Parallel Hash Join crash when work_mem is small
Date: Sun, 09 Nov 2025 18:40:55 -0500
Message-ID: <1715740.1762731655@sss.pgh.pa.us> (raw)
In-Reply-To: <CA+hUKGJwCNT_mSZQn8XYzF+PV4GzgSBNEcAS6ouyso+4-RpXDA@mail.gmail.com>
References: <19105-7516b55f7ed3a241@postgresql.org>
<CA+hUKGJwCNT_mSZQn8XYzF+PV4GzgSBNEcAS6ouyso+4-RpXDA@mail.gmail.com>
Thomas Munro <thomas.munro@gmail.com> writes:
> On Mon, Nov 10, 2025 at 4:23 AM PG Bug reporting form
> <noreply@postgresql.org> wrote:
>> ERROR: could not attach to dynamic shared area
>> DETAIL: invalid dsa_handle
> ereport(ERROR,
> (errcode(ERRCODE_OBJECT_NOT_IN_PREREQUISITE_STATE),
> errmsg("could not attach to dynamic shared area")));
> Where do we emit that DETAIL message?
I'd not picked up on that point, but you're right: we don't emit any
such DETAIL anywhere, not in current and not in 16.2 either. Must
be a locally-modified tree, or maybe just a copy-paste error in the
report?
regards, tom lane
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: tgl@sss.pgh.pa.us, thomas.munro@gmail.com, nageshdbaa@gmail.com, pgsql-bugs@lists.postgresql.org
Subject: Re: BUG #19105: Parallel Hash Join crash when work_mem is small
In-Reply-To: <1715740.1762731655@sss.pgh.pa.us>
* 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