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+TgmoZATLS6R+u-QSWOMKuNSGJKYwRasycny=LAG9D0OsG7OQ@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 Thu, Mar 28, 2024 at 11:50 AM Tom Lane <tgl@sss.pgh.pa.us> wrote:
> Yeah, I was thinking about that too.  The normal case is that you
> don't hold any releasable resources except locks when arriving at
> CommitSubTransaction --- if you do, it's a bug and we're going to
> print leak warnings.  Seems like maybe it'd be worth trying to
> have a fast path for that case.

Well, there's the abort case, too, which I think is almost equally important.

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



pgsql-hackers by date:

Previous
From: Alvaro Herrera
Date:
Subject: Re: ALTER TABLE SET ACCESS METHOD on partitioned tables
Next
From: Tom Lane
Date:
Subject: Re: [PATCH] plpython function causes server panic