Re: BUG #19480: PL/Python SRF crashes (SIGSEGV) when function is replaced mid-iteration: use-after-free in PLy_funct
Tom Lane <tgl@sss.pgh.pa.us>
From: Tom Lane <tgl@sss.pgh.pa.us>
To: Heikki Linnakangas <hlinnaka@iki.fi>
Cc: Matheus Alcantara <matheusssilv97@gmail.com>, adoros@starfishstorage.com,
pgsql-bugs@lists.postgresql.org, rmt@lists.postgresql.org
Date: 2026-06-17T15:56:36Z
Lists: pgsql-bugs
Heikki Linnakangas <hlinnaka@iki.fi> 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
Commits
Same data as JSON:
GET /api/v1/messages/:b64id/commits
the thread's linked commits as JSON, with link sources.
API reference →
-
plpython: Use funccache.c infrastructure for procedure caching.
- 9bcb8a694b3b 19 (unreleased) landed