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

From: shihao zhong <zhong950419(at)gmail(dot)com>
To: Andrey Rachitskiy <pl0h0yp1(at)gmail(dot)com>
Cc: Robert Haas <robertmhaas(at)gmail(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, 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-19 05:09:11
Message-ID: CAGRkXqTm1a4ENoRph+u0iDf+QEyGEef4dWVc1bkV3+AX0eNDkg@mail.gmail.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

Hi Andrey,

Thanks for your patches.

> In 0002 I fixed other problematic spots in pl_python.

Thanks for the v3. I ran the same allocation failure tests and it
doesn't crash. It also fixes a crash in PLy_procedure_compile() that my
v2 missed.

Thanks,
Shihao

In response to

Browse pgsql-bugs by date

  From Date Subject
Next Message Fujii Masao 2026-11-19 07:14:21 Re: BUG #19776: pg_combinebackup ignores the truncation_block_length of an intermediate incremental backup
Previous Message shihao zhong 2026-11-19 05:06:11 Re: BUG #19893: REPLICA IDENTITY FULL: UPDATE/DELETE skipped when a subscriber-only column has a value