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 1sLmDG-00GVaK-Gm for pgsql-bugs@arkaria.postgresql.org; Mon, 24 Jun 2024 16:06:38 +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 1sLmDE-00ASEb-SJ for pgsql-bugs@arkaria.postgresql.org; Mon, 24 Jun 2024 16:06:37 +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 ) id 1sLmDE-00ASET-K2 for pgsql-bugs@lists.postgresql.org; Mon, 24 Jun 2024 16:06:36 +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 ) id 1sLmDC-003KVJ-LB for pgsql-bugs@lists.postgresql.org; Mon, 24 Jun 2024 16:06:36 +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 45OG6TND1168680; Mon, 24 Jun 2024 12:06:29 -0400 From: Tom Lane To: Alvaro Herrera cc: Tender Wang , 1026592243@qq.com, pgsql-bugs@lists.postgresql.org Subject: Re: BUG #18377: Assert false in "partdesc->nparts >= pinfo->nparts", fileName="execPartition.c", lineNumber=1943 In-reply-to: <202406241517.ugtdq7tokfnx@alvherre.pgsql> References: <202406241517.ugtdq7tokfnx@alvherre.pgsql> Comments: In-reply-to Alvaro Herrera message dated "Mon, 24 Jun 2024 17:17:04 +0200" MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <1168678.1719245189.1@sss.pgh.pa.us> Date: Mon, 24 Jun 2024 12:06:29 -0400 Message-ID: <1168679.1719245189@sss.pgh.pa.us> List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk Alvaro Herrera writes: > Sigh. No, I missed that. I'm going to revert it now, because I see that > skink failed. I don't see how my patch is to blame since it's a timeout > and we have no logs for the failure; but maybe my patch did make > something slower and caused some test to go over the time limit. skink's been doing that intermittently for some time; I wouldn't assume this patch is especially to blame. Given the lack of other failures, maybe you should leave it as-is. It's not really per policy, but after all this is just a beta ... regards, tom lane