Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1vIF1r-000rAe-R1 for pgsql-bugs@arkaria.postgresql.org; Sun, 09 Nov 2025 23:41:03 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.94.2) (envelope-from ) id 1vIF1n-00BIA3-Me for pgsql-bugs@arkaria.postgresql.org; Sun, 09 Nov 2025 23:40:59 +0000 Received: from makus.postgresql.org ([2001:4800:3e1:1::229]) by malur.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1vIF1n-00BI8v-DY for pgsql-bugs@lists.postgresql.org; Sun, 09 Nov 2025 23:40:59 +0000 Received: from sss.pgh.pa.us ([68.162.161.243]) by makus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.96) (envelope-from ) id 1vIF1l-006Han-1A for pgsql-bugs@lists.postgresql.org; Sun, 09 Nov 2025 23:40:58 +0000 Received: from sss1.sss.pgh.pa.us (localhost [127.0.0.1]) by sss.pgh.pa.us (8.15.2/8.15.2) with ESMTP id 5A9Net641715741; Sun, 9 Nov 2025 18:40:55 -0500 From: Tom Lane To: Thomas Munro cc: nageshdbaa@gmail.com, pgsql-bugs@lists.postgresql.org Subject: Re: BUG #19105: Parallel Hash Join crash when work_mem is small In-reply-to: References: <19105-7516b55f7ed3a241@postgresql.org> Comments: In-reply-to Thomas Munro message dated "Mon, 10 Nov 2025 11:35:10 +1300" MIME-Version: 1.0 Content-Type: text/plain; charset="UTF-8" Content-ID: <1715739.1762731655.1@sss.pgh.pa.us> Content-Transfer-Encoding: 8bit Date: Sun, 09 Nov 2025 18:40:55 -0500 Message-ID: <1715740.1762731655@sss.pgh.pa.us> List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk Thomas Munro writes: > On Mon, Nov 10, 2025 at 4:23 AM PG Bug reporting form > 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