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 1o7GXb-0003QF-G8 for pgsql-performance@arkaria.postgresql.org; Fri, 01 Jul 2022 13:18:35 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1o7GXa-00008H-Df for pgsql-performance@arkaria.postgresql.org; Fri, 01 Jul 2022 13:18:34 +0000 Received: from makus.postgresql.org ([2001:4800:3e1:1::229]) by malur.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1o7GXa-00089p-3t for pgsql-performance@lists.postgresql.org; Fri, 01 Jul 2022 13:18:34 +0000 Received: from sss.pgh.pa.us ([66.207.139.130]) by makus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1o7GXX-0004D7-I1 for pgsql-performance@lists.postgresql.org; Fri, 01 Jul 2022 13:18:33 +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 261DIS0Y712770; Fri, 1 Jul 2022 09:18:28 -0400 From: Tom Lane To: Justin Pryzby cc: "James Pang (chaolpan)" , pgsql-performance@lists.postgresql.org Subject: Re: partition pruning only works for select but update In-reply-to: <20220701131311.GC13040@telsasoft.com> References: <2391513.1656423000@sss.pgh.pa.us> <20220701131311.GC13040@telsasoft.com> Comments: In-reply-to Justin Pryzby message dated "Fri, 01 Jul 2022 08:13:11 -0500" MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <712768.1656681508.1@sss.pgh.pa.us> Content-Transfer-Encoding: quoted-printable Date: Fri, 01 Jul 2022 09:18:28 -0400 Message-ID: <712769.1656681508@sss.pgh.pa.us> List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk Justin Pryzby writes: > On Fri, Jul 01, 2022 at 08:30:40AM +0000, James Pang (chaolpan) wrote: >> We have other application depend on V13, possible to backport code chan= ges to V13 as https://git.postgresql.org/gitweb/?p=3Dpostgresql.git;a=3Dpa= tch;h=3D86dc90056dfdbd9d1b891718d2e5614e3e432f35 > In any case, I'm sure the feature won't be backpatched to v13 - it's an > improvement but not a bugfix. Even more to the point, it was an extremely major change and would take a huge amount of QA effort to ensure that dropping it into v13 wouldn't cause fresh problems. The PG community has exactly no interest in making such effort. Besides which, what do you imagine "depends on v13" actually means? If you have an app that works on v13 but not v14, maybe it's because it depends on the old behavior in some way. Spend your effort on updating your app, instead. regards, tom lane