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 1rfN27-00HFER-5z for pgsql-bugs@arkaria.postgresql.org; Wed, 28 Feb 2024 16:43:51 +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 1rfN25-00CCpc-Ne for pgsql-bugs@arkaria.postgresql.org; Wed, 28 Feb 2024 16:43:50 +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 1rfN25-00CCpS-FU for pgsql-bugs@lists.postgresql.org; Wed, 28 Feb 2024 16:43:49 +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.94.2) (envelope-from ) id 1rfN22-001qiL-FZ for pgsql-bugs@lists.postgresql.org; Wed, 28 Feb 2024 16:43:48 +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 41SGhjMg2318014; Wed, 28 Feb 2024 11:43:45 -0500 From: Tom Lane To: "GADACHA Rachid (Acoss)" cc: "pgsql-bugs@lists.postgresql.org" Subject: Re: [Bugg hash join and parallel worker] In-reply-to: References: <2316484.1709137799@sss.pgh.pa.us> Comments: In-reply-to "GADACHA Rachid (Acoss)" message dated "Wed, 28 Feb 2024 16:33:08 +0000" MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <2318012.1709138625.1@sss.pgh.pa.us> Content-Transfer-Encoding: quoted-printable Date: Wed, 28 Feb 2024 11:43:45 -0500 Message-ID: <2318013.1709138625@sss.pgh.pa.us> List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk "GADACHA Rachid (Acoss)" writes: > I can't reproduce the scenario, because we don't have the current minor = release (13.14). If you're unwilling to update to a new minor release, how do you think we could help you? If the bug's still there (which it might not be) any fix would appear in a future minor release. There's nothing we can do now about the behavior of 13.2. regards, tom lane