| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Heikki Linnakangas <hlinnaka(at)iki(dot)fi> |
| Cc: | Matheus Alcantara <matheusssilv97(at)gmail(dot)com>, adoros(at)starfishstorage(dot)com, pgsql-bugs(at)lists(dot)postgresql(dot)org, rmt(at)lists(dot)postgresql(dot)org |
| Subject: | Re: BUG #19480: PL/Python SRF crashes (SIGSEGV) when function is replaced mid-iteration: use-after-free in PLy_funct |
| Date: | 2026-06-17 15:56:36 |
| Message-ID: | 1125803.1781711796@sss.pgh.pa.us |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
Heikki Linnakangas <hlinnaka(at)iki(dot)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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Сергей Дм. Апойченко | 2026-06-17 16:49:22 | Re: BUG #19521: After a minor PostgreSQL update from 14.22 to 14.23, the database goes into an infinite loop. |
| Previous Message | Melanie Plageman | 2026-06-17 15:43:43 | Re: BUG #19480: PL/Python SRF crashes (SIGSEGV) when function is replaced mid-iteration: use-after-free in PLy_funct |