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

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

Hi,

17.09.2023 07:25, Michael Paquier wrote:
> Thanks. It's a long weekend here as well, so I'll be able to do
> anything serious only in 48 hours or so (aka being able to check on
> the buildfarm). If you have the room to send patches for the
> back-branches until then, that would be super helpful, of course!

Please look at the patches for backpatching (I think they meet our
agreements) and also the new main patch (which perhaps a step closer to
expectations).

Best regards,
Alexander

Attachment Content-Type Size
v4-01-fix-plpy_elog.backpatch12- text/plain 3.7 KB
v4-01-fix-plpy_elog.backpatch14- text/plain 2.8 KB
v4-01-fix-plpy_elog.backpatch16- text/plain 2.8 KB
v4-01-fix-plpy_elog.patch text/x-patch 3.6 KB

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Michael Paquier 2023-09-18 10:13:50 Re: BUG #18070: Assertion failed when processing error from plpy's iterator
Previous Message Richard Guo 2023-09-18 06:44:07 Re: BUG #18103: bugs of concurrent merge into when use different join plan