Re: [PATCH] plpython function causes server panic
Tom Lane <tgl@sss.pgh.pa.us>
From: Tom Lane <tgl@sss.pgh.pa.us>
To: Robert Haas <robertmhaas@gmail.com>
Cc: Hao Zhang <zhrt1446384557@gmail.com>, Andres Freund <andres@anarazel.de>,
pgsql-hackers@lists.postgresql.org
Date: 2024-03-28T16:01:37Z
Lists: pgsql-hackers
Robert Haas <robertmhaas@gmail.com> writes: > 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. True, but in the abort case there probably *are* resources to be cleaned up, so I'm not seeing that the fast-path idea helps. Although maybe the idea of batching multiple cleanups would? regards, tom lane
Commits
-
Allow "internal" subtransactions in parallel mode.
- 0075d78947e3 17.0 landed
-
Tighten up application of parallel mode checks.
- 94b4f7e2a635 9.6.0 cited