Re: BUG #19480: PL/Python SRF crashes (SIGSEGV) when function is replaced mid-iteration: use-after-free in PLy_funct

Nathan Bossart <nathandbossart@gmail.com>

From: Nathan Bossart <nathandbossart@gmail.com>
To: Heikki Linnakangas <hlinnaka@iki.fi>
Cc: Matheus Alcantara <matheusssilv97@gmail.com>, Tom Lane <tgl@sss.pgh.pa.us>, adoros@starfishstorage.com, pgsql-bugs@lists.postgresql.org, rmt@lists.postgresql.org
Date: 2026-06-17T15:43:06Z
Lists: pgsql-bugs
On Wed, Jun 17, 2026 at 06:30:30PM +0300, Heikki Linnakangas wrote:
> 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.
> 
> 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.

+1

-- 
nathan



Commits

Same data as JSON: GET /api/v1/messages/:b64id/commits the thread's linked commits as JSON, with link sources. API reference →
  1. plpython: Use funccache.c infrastructure for procedure caching.