Re: BUG #18070: Assertion failed when processing error from plpy's iterator - Mailing list pgsql-bugs

From Tom Lane
Subject Re: BUG #18070: Assertion failed when processing error from plpy's iterator
Date
Msg-id 3984911.1694908923@sss.pgh.pa.us
Whole thread Raw
In response to Re: BUG #18070: Assertion failed when processing error from plpy's iterator  (Michael Paquier <michael@paquier.xyz>)
Responses Re: BUG #18070: Assertion failed when processing error from plpy's iterator
List pgsql-bugs
Michael Paquier <michael@paquier.xyz> writes:
> Btw, backpatching a change in the error infrastructure does not seem a
> good idea to me, as there could be applications that depend on the
> existing behaviors?  It looks like we'd better just remove the
> assertion in back-branches.

+1.  Not very sure what we want to change this to in HEAD, but
I wouldn't backpatch a behavioral change here.

            regards, tom lane



pgsql-bugs by date:

Previous
From: Michael Paquier
Date:
Subject: Re: BUG #18070: Assertion failed when processing error from plpy's iterator
Next
From: Wèi Cōngruì
Date:
Subject: Re: BUG #18114: FULL JOIN is replaced by LEFT JOIN in plan