Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1k3O3C-0005qH-9Z for pgsql-hackers@arkaria.postgresql.org; Wed, 05 Aug 2020 18:22:06 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1k3O3B-0000nJ-3G for pgsql-hackers@arkaria.postgresql.org; Wed, 05 Aug 2020 18:22:05 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1k3O3A-0000nC-SI for pgsql-hackers@lists.postgresql.org; Wed, 05 Aug 2020 18:22:04 +0000 Received: from sss.pgh.pa.us ([66.207.139.130]) by magus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1k3O38-0006JN-1l for pgsql-hackers@postgresql.org; Wed, 05 Aug 2020 18:22:04 +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 075ILx492550498; Wed, 5 Aug 2020 14:21:59 -0400 From: Tom Lane To: Robert Haas cc: Amit Langote , Justin Pryzby , "pgsql-hackers@postgresql.org" Subject: Re: FailedAssertion("pd_idx == pinfo->nparts", File: "execPartition.c", Line: 1689) In-reply-to: References: <20200802181131.GA27754@telsasoft.com> <20200803161133.GA21372@telsasoft.com> <2528807.1596648630@sss.pgh.pa.us> Comments: In-reply-to Robert Haas message dated "Wed, 05 Aug 2020 13:53:03 -0400" MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <2550496.1596651719.1@sss.pgh.pa.us> Date: Wed, 05 Aug 2020 14:21:59 -0400 Message-ID: <2550497.1596651719@sss.pgh.pa.us> List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk Robert Haas writes: > On Wed, Aug 5, 2020 at 1:30 PM Tom Lane wrote: >> I'm strongly tempted to convert the trailing Assert to an actual >> test-and-elog, too, but didn't do so here. > I was thinking about that, too. +1 for taking that step. Will do. In the longer term, it's annoying that we have no test methodology for this other than "manually set a breakpoint here". If we're going to allow plan-relevant DDL changes to happen with less than full table lock, I think we need to improve that. I spent a little bit of time just now trying to build an isolationtester case for this, and failed completely. So I wonder if we can create some sort of test module that allows capture of a plan tree and then execution of that plan tree later (even after relcache inval would normally have forced replanning). Obviously that could not be a normal SQL-accessible feature, because some types of invals would make the plan completely wrong, but for testing purposes it'd be mighty helpful to check that a stale plan still works. regards, tom lane