Re: BUG #18070: Assertion failed when processing error from plpy's iterator

From: Michael Paquier <michael(at)paquier(dot)xyz>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Alexander Lakhin <exclusion(at)gmail(dot)com>, pgsql-bugs(at)lists(dot)postgresql(dot)org
Subject: Re: BUG #18070: Assertion failed when processing error from plpy's iterator
Date: 2023-09-17 01:50:36
Message-ID: ZQZbbPA7NC5A0f4i@paquier.xyz
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

On Sat, Sep 16, 2023 at 08:02:03PM -0400, Tom Lane wrote:
> +1. Not very sure what we want to change this to in HEAD, but
> I wouldn't backpatch a behavioral change here.

Please find attached a proposal of patch for a backpatch, that applies
on HEAD. The backpatch needs a few tweaks for alternate outputs, of
course, depending on the version of python.

Any thoughts?
--
Michael

Attachment Content-Type Size
v3-01-fix-plpy_elog.patch text/x-diff 2.8 KB

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Michael Paquier 2023-09-17 01:58:56 Re: BUG #18108: server process was terminated by signal 11: Segmentation fault
Previous Message Wèi Cōngruì 2023-09-17 01:03:21 Re: BUG #18114: FULL JOIN is replaced by LEFT JOIN in plan