Re: After 10 -> 15 upgrade getting "cannot commit while a portal is pinned" on one python function - Mailing list pgsql-general

From Tom Lane
Subject Re: After 10 -> 15 upgrade getting "cannot commit while a portal is pinned" on one python function
Date
Msg-id 133886.1710975858@sss.pgh.pa.us
Whole thread Raw
In response to Re: After 10 -> 15 upgrade getting "cannot commit while a portal is pinned" on one python function  (Adrian Klaver <adrian.klaver@aklaver.com>)
Responses Re: After 10 -> 15 upgrade getting "cannot commit while a portal is pinned" on one python function  (Jeff Ross <jross@openvistas.net>)
List pgsql-general
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



pgsql-general by date:

Previous
From: Adrian Klaver
Date:
Subject: Re: After 10 -> 15 upgrade getting "cannot commit while a portal is pinned" on one python function
Next
From: Adrian Klaver
Date:
Subject: Re: After 10 -> 15 upgrade getting "cannot commit while a portal is pinned" on one python function