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

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Michael Paquier <michael(at)paquier(dot)xyz>
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 00:02:03
Message-ID: 3984911.1694908923@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

Michael Paquier <michael(at)paquier(dot)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

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Wèi Cōngruì 2023-09-17 01:03:21 Re: BUG #18114: FULL JOIN is replaced by LEFT JOIN in plan
Previous Message Michael Paquier 2023-09-16 23:50:13 Re: BUG #18070: Assertion failed when processing error from plpy's iterator