From: Tom Lane <tgl@sss.pgh.pa.us>
To: Adrian Klaver <adrian.klaver@aklaver.com>
cc: Jeff Ross <jross@openvistas.net>, pgsql-general@lists.postgresql.org
Subject: Re: After 10 -> 15 upgrade getting "cannot commit while a portal is
 pinned" on one python function
In-reply-to: <37154728-4700-45b7-9261-72400c80b12b@aklaver.com>
References: <6960da61-8033-4067-84d1-d9257ce94870@openvistas.net>
 <81c4556d-b599-4512-b6a2-7255f2a39089@aklaver.com>
 <d553c7d6-8af9-4e93-892b-7dc65129b4a6@openvistas.net>
 <37154728-4700-45b7-9261-72400c80b12b@aklaver.com>
Comments: In-reply-to Adrian Klaver <adrian.klaver@aklaver.com>
	message dated "Wed, 20 Mar 2024 15:56:17 -0700"
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-ID: <133885.1710975858.1@sss.pgh.pa.us>
Date: Wed, 20 Mar 2024 19:04:18 -0400
Message-ID: <133886.1710975858@sss.pgh.pa.us>
Archived-At: 
 <https://www.postgresql.org/message-id/133886.1710975858%40sss.pgh.pa.us>
Precedence: bulk

Adrian Klaver <adrian.klaver@aklaver.com> writes:
> Haven't had a chance to go through this yet. I'm going to say though 
> that Tom Lane is looking for a shorter generic case that anyone could 
> run on their system.

Yeah, it's a long way from that trigger function definition to a
working (i.e. failing) example.  Shortening the trigger might help by
eliminating some parts of the infrastructure that would need to be
shown --- but nobody's going to try to reverse-engineer all that.

			regards, tom lane