| From: | Adrian Klaver <adrian(dot)klaver(at)aklaver(dot)com> |
|---|---|
| To: | Jeff Ross <jross(at)openvistas(dot)net>, "pgsql-general(at)lists(dot)postgresql(dot)org" <pgsql-general(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: After 10 -> 15 upgrade getting "cannot commit while a portal is pinned" on one python function |
| Date: | 2024-03-20 22:25:54 |
| Message-ID: | 81c4556d-b599-4512-b6a2-7255f2a39089@aklaver.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On 3/20/24 15:18, Jeff Ross wrote:
> Greetings!
>
> I built a trigger fired process that copies an "order" from our
> production database to our dev database. An order, in this case, is an
> initial row from a table and all of the rows in all of the tables in
> that database/schema that are needed to satisfy all of the foreign key
> constraints for the original insert. Through a web page, one of our
> folks can select a schema and an order id to copy. That information is
> then inserted into a table. A trigger attached to that table takes care
> of copying the necessary rows using a function that uses both plython3u
> and psycopg2. I can supply the source code if that will help.
I think that will help, especially the interaction between psycopg2 and
plpython3u.
--
Adrian Klaver
adrian(dot)klaver(at)aklaver(dot)com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2024-03-20 22:50:36 | Re: After 10 -> 15 upgrade getting "cannot commit while a portal is pinned" on one python function |
| Previous Message | Jeff Ross | 2024-03-20 22:18:58 | After 10 -> 15 upgrade getting "cannot commit while a portal is pinned" on one python function |