Re: BUG #19899: PL/Python backend crashes (SIGSEGV) when converting a column value to a Python object fails

From: Andrey Rachitskiy <pl0h0yp1(at)gmail(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: marcos(dot)castedo(at)anachronics(dot)com, pgsql-bugs(at)lists(dot)postgresql(dot)org
Subject: Re: BUG #19899: PL/Python backend crashes (SIGSEGV) when converting a column value to a Python object fails
Date: 2026-11-16 19:10:39
Message-ID: CAB8bMit7rCwmb3x3-U-rMB91Wp07iLGrGGJLsdUnpO2e7S07Ug@mail.gmail.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

пн, 16 нояб. 2026 г. в 22:53, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>:

> I think
> we'd first want to decide whether to check immediately after
> each call to a Python function, or try to centralize it a bit.
>
>
Hi Tom!

I centralized the problematic spots in plpy_typeio - a small step toward
order.
I'll look at the other places in plpython a bit later.

Thoughts?

--
Regards,
Rachitskiy Andrey

Attachment Content-Type Size
0001-Fix-unchecked-NULL-returns-in-PL-Python-type-convers.patch text/x-patch 8.1 KB

In response to

Browse pgsql-bugs by date

  From Date Subject
Next Message Andres Freund 2026-11-16 19:14:32 Re: Two bugs around ALTER TYPE
Previous Message shihao zhong 2026-11-16 19:07:52 Re: PostgreSQL 18.6/17.11: standby PANIC on restart after VM truncation