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 <pgsql-bugs-owner+archive@lists.postgresql.org>)
	id 1tTNVY-0059uO-R1
	for pgsql-bugs@arkaria.postgresql.org; Thu, 02 Jan 2025 15:53:13 +0000
Received: from localhost ([127.0.0.1] helo=malur.postgresql.org)
	by malur.postgresql.org with esmtp (Exim 4.94.2)
	(envelope-from <pgsql-bugs-owner+archive@lists.postgresql.org>)
	id 1tTNVX-00Gfd8-9k
	for pgsql-bugs@arkaria.postgresql.org; Thu, 02 Jan 2025 15:53:11 +0000
Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29])
	by malur.postgresql.org with esmtps  (TLS1.3) tls
 TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384
	(Exim 4.94.2)
	(envelope-from <tgl@sss.pgh.pa.us>)
	id 1tTNVX-00Gfd0-12
	for pgsql-bugs@lists.postgresql.org; Thu, 02 Jan 2025 15:53:10 +0000
Received: from sss.pgh.pa.us ([68.162.161.243])
	by magus.postgresql.org with esmtps  (TLS1.3) tls
 TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384
	(Exim 4.94.2)
	(envelope-from <tgl@sss.pgh.pa.us>)
	id 1tTNVT-002qbP-Mv
	for pgsql-bugs@lists.postgresql.org; Thu, 02 Jan 2025 15:53:10 +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 502Fr1jU268543;
	Thu, 2 Jan 2025 10:53:01 -0500
From: Tom Lane <tgl@sss.pgh.pa.us>
To: "Rank, Christian (LfL)" <Christian.Rank@lfl.bayern.de>
cc: Laurenz Albe <laurenz.albe@cybertec.at>,
        "pgsql-bugs@lists.postgresql.org" <pgsql-bugs@lists.postgresql.org>,
        "PostgreSQL TDBA (LDBV)" <PostgreSQL_TDBA@ldbv.bayern.de>
Subject: Re: AW: Commit 5a2fed911a broke parallel query
In-reply-to: <2fe29e302a9849d6a84f7a0ae0f54210@lfl.bayern.de>
References: <8befc845430ba1ae3748af900af298788e579c89.camel@cybertec.at>
 <2fe29e302a9849d6a84f7a0ae0f54210@lfl.bayern.de>
Comments: In-reply-to "Rank, Christian (LfL)" <Christian.Rank@lfl.bayern.de>
	message dated "Thu, 02 Jan 2025 09:33:36 +0000"
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-ID: <268541.1735833181.1@sss.pgh.pa.us>
Content-Transfer-Encoding: quoted-printable
Date: Thu, 02 Jan 2025 10:53:01 -0500
Message-ID: <268542.1735833181@sss.pgh.pa.us>
List-Id: <pgsql-bugs.lists.postgresql.org>
List-Help: <https://lists.postgresql.org/manage/>
List-Subscribe: <https://lists.postgresql.org/manage/>
List-Post: <mailto:pgsql-bugs@lists.postgresql.org>
List-Owner: <mailto:pgsql-bugs-owner@lists.postgresql.org>
List-Archive: <https://www.postgresql.org/list/pgsql-bugs>
Archived-At: 
 <https://www.postgresql.org/message-id/268542.1735833181%40sss.pgh.pa.us>
Precedence: bulk

"Rank, Christian (LfL)" <Christian.Rank@lfl.bayern.de> writes:
> just a notice that this sounds like the symptom already described in
> 	https://www.postgresql.org/message-id/c7896c19adb646e889d5b2e40fdd17c1@=
ldbv.bayern.de

Indeed.  My apologies for having not gotten back to you in that
thread.  There is a committed fix now:

https://git.postgresql.org/gitweb/?p=3Dpostgresql.git;a=3Dcommitdiff;h=3D4=
1a252c2ca68ba7239e73abd99fdbf28871f5f07

(caution: the fix is nontrivially different in each branch; that
one is for v16)

			regards, tom lane