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.96) (envelope-from ) id 1wZsdD-001Mk1-1s for pgsql-bugs@arkaria.postgresql.org; Wed, 17 Jun 2026 15:56:47 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.96) (envelope-from ) id 1wZsdC-006iwB-1K for pgsql-bugs@arkaria.postgresql.org; Wed, 17 Jun 2026 15:56:46 +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.96) (envelope-from ) id 1wZsdC-006ivo-05; Wed, 17 Jun 2026 15:56:46 +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.98.2) (envelope-from ) id 1wZsdA-00000000pPI-0BmR; Wed, 17 Jun 2026 15:56:44 +0000 Received: from sss1.sss.pgh.pa.us (localhost [127.0.0.1]) by sss.pgh.pa.us (8.18.1/8.18.1) with ESMTP id 65HFuaci1125804; Wed, 17 Jun 2026 11:56:36 -0400 From: Tom Lane To: Heikki Linnakangas cc: Matheus Alcantara , adoros@starfishstorage.com, pgsql-bugs@lists.postgresql.org, rmt@lists.postgresql.org Subject: Re: BUG #19480: PL/Python SRF crashes (SIGSEGV) when function is replaced mid-iteration: use-after-free in PLy_funct In-reply-to: References: <19480-f1f9fdce30462fc4@postgresql.org> <982975.1779981146@sss.pgh.pa.us> <2868592.1780356411@sss.pgh.pa.us> <3770958.1780686685@sss.pgh.pa.us> <9ecd2bd5-0fec-4ec2-9800-eb071683128c@gmail.com> Comments: In-reply-to Heikki Linnakangas message dated "Wed, 17 Jun 2026 18:30:30 +0300" MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <1125802.1781711796.1@sss.pgh.pa.us> Date: Wed, 17 Jun 2026 11:56:36 -0400 Message-ID: <1125803.1781711796@sss.pgh.pa.us> List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk Heikki Linnakangas writes: >>>> Looping in the RMT to see what they think... > It's fine to still sneak it into v19. It's better to have it earlier, > even if it means more churn during beta period. OK. I haven't looked closely at the patch yet, but will proceed with reviewing it. > I haven't looked closely at the patch, but since it's a bug fix it would > make sense to backpatch. If we're uncomfortable with backpatching it > now, we could commit in master now, and backpatch later when we have > more confidence. I'm of the opinion that the risk-reward ratio is not great for putting this into stable branches. The case that fails is just not something I'd expect people to do a lot in production. So I'm content with sneaking it into v19. regards, tom lane