Feedback-ID: i76984098:Fastmail
Message-ID: <a27826a2-9f22-4a5c-a0f2-cfe5dbc156c4@aklaver.com>
Date: Thu, 21 Mar 2024 09:30:55 -0700
MIME-Version: 1.0
User-Agent: Mozilla Thunderbird
Subject: Re: After 10 -> 15 upgrade getting "cannot commit while a portal is
 pinned" on one python function
Content-Language: en-US
To: Jeff Ross <jross@openvistas.net>, psycopg@lists.postgresql.org
References: <7b43f00b-5033-4975-b882-252cfcf40c54@openvistas.net>
From: Adrian Klaver <adrian.klaver@aklaver.com>
In-Reply-To: <7b43f00b-5033-4975-b882-252cfcf40c54@openvistas.net>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
Archived-At: 
 <https://www.postgresql.org/message-id/a27826a2-9f22-4a5c-a0f2-cfe5dbc156c4%40aklaver.com>
Precedence: bulk

On 3/21/24 09:06, Jeff Ross wrote:
> Greetings!
> 
> I posted a version of this to the pgsql-general mailing list yesterday.  
> Since then I've narrowed down the error to this line:
> 
> prod_database_connection.commit()
> 
> so I believe this is psycopg2 related.

Does it work outside of plpython3u?

> 
> This is on CentOS 7 and I'm using python3-psycopg2.x86_64 2.8.6-1.rhel7 
> installed from yum.

psycopg2 is up to 2.9.9. You are missing ~3 years of fixes.

> 
> makes me wonder if this error is specific to plpython3?

Hard to say as the other bug report you linked to seemed to refer to 
plpythonu.


> Jeff
> 
> 

-- 
Adrian Klaver
adrian.klaver@aklaver.com