From: Tom Lane <tgl@sss.pgh.pa.us>
To: Jeff Ross <jross@openvistas.net>
Cc: pgsql-general@lists.postgresql.org <pgsql-general@lists.postgresql.org>
Subject: Re: After 10 -> 15 upgrade getting "cannot commit while a portal is pinned" on one python function
Date: Wed, 20 Mar 2024 18:50:36 -0400
Message-ID: <131796.1710975036@sss.pgh.pa.us> (raw)
In-Reply-To: <6960da61-8033-4067-84d1-d9257ce94870@openvistas.net>
References: <6960da61-8033-4067-84d1-d9257ce94870@openvistas.net>
Jeff Ross <jross@openvistas.net> writes:
> I then get this error:
> NOTICE: update cargotel_common.copy_orders_to_dev set copy_completed =
> 't', copy_completed_timestamp = clock_timestamp() where id = 21
> ERROR: cannot commit while a portal is pinned
Would you mind supplying a self-contained example that triggers this?
regards, tom lane
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-general@postgresql.org
Cc: tgl@sss.pgh.pa.us, 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: <131796.1710975036@sss.pgh.pa.us>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox