Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.89) (envelope-from ) id 1j098R-0007HT-0q for pgsql-bugs@arkaria.postgresql.org; Fri, 07 Feb 2020 19:17:51 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.89) (envelope-from ) id 1j098P-000820-RS for pgsql-bugs@arkaria.postgresql.org; Fri, 07 Feb 2020 19:17:49 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.89) (envelope-from ) id 1j098P-00081t-JH for pgsql-bugs@lists.postgresql.org; Fri, 07 Feb 2020 19:17:49 +0000 Received: from sss.pgh.pa.us ([66.207.139.130]) by magus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1j098N-0004FY-Bz for pgsql-bugs@lists.postgresql.org; Fri, 07 Feb 2020 19:17:49 +0000 Received: from sss1.sss.pgh.pa.us (localhost [127.0.0.1]) by sss.pgh.pa.us (8.14.4/8.14.4) with ESMTP id 017JHiJS029416; Fri, 7 Feb 2020 14:17:44 -0500 From: Tom Lane To: boekewurm+postgres@gmail.com cc: pgsql-bugs@lists.postgresql.org Subject: Re: BUG #16249: Partition pruning blocks on exclusively locked table partition In-reply-to: <16249-0008721939743475@postgresql.org> References: <16249-0008721939743475@postgresql.org> Comments: In-reply-to PG Bug reporting form message dated "Fri, 07 Feb 2020 19:10:05 +0000" MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <29414.1581103064.1@sss.pgh.pa.us> Date: Fri, 07 Feb 2020 14:17:44 -0500 Message-ID: <29415.1581103064@sss.pgh.pa.us> List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk PG Bug reporting form writes: > In my humble opinion, this query should not be blocked during planning, as > the partition can be pruned directly from the plan with the partition > information that is available from the parent table: Partition information > can be updated when the partition is locked, but through the parent > partitioned table. This case has been improved in PG v12. It is operating as designed in v11, however. regards, tom lane