Re: [PATCH] plpython function causes server panic - Mailing list pgsql-hackers

From Robert Haas
Subject Re: [PATCH] plpython function causes server panic
Date
Msg-id CA+Tgmoa4bhNFe7cU8_MnLx-JEC3aRciq3kXnJbHUJQ4j9-xgWA@mail.gmail.com
Whole thread Raw
In response to Re: [PATCH] plpython function causes server panic  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: [PATCH] plpython function causes server panic
List pgsql-hackers
On Mon, Mar 25, 2024 at 11:36 AM Tom Lane <tgl@sss.pgh.pa.us> wrote:
> By that logic, we should rip out every Assert in the system, as well
> as all of the (extensive) resource leak checking that already happens
> during CommitTransaction.  We've always felt that those leak checks
> were worth the cost to help us find bugs --- which they have done and
> still do from time to time.  I don't see why this case is different,
> especially when the added cost compared to HEAD is not much more than
> one C function call.

Well, I explained why *I* thought it was different, but obviously you
don't agree.

--
Robert Haas
EDB: http://www.enterprisedb.com



pgsql-hackers by date:

Previous
From: Robert Haas
Date:
Subject: Re: pgsql: Track last_inactive_time in pg_replication_slots.
Next
From: Robert Haas
Date:
Subject: Re: documentation structure