Re: Why plpython functions increase transaction counter much more then plpgsql functions?

From: Michał Albrycht <michalalbrycht(at)gmail(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: pgsql-general(at)lists(dot)postgresql(dot)org
Subject: Re: Why plpython functions increase transaction counter much more then plpgsql functions?
Date: 2024-11-08 17:44:40
Message-ID: CACsoHGCsXBYbv__t2xDVxth1EroBTsO=SnfJror4HCy-XtN4Lg@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

>
> A quick look at PLy_spi_execute_query shows that it runs each command
> in a subtransaction. It pretty much has to, because the coding rules
> for a Python method don't permit it to just longjmp out of the Python
> interpreter, so it has to set up a subtransaction so it can catch any
> error. In this example, each subtransaction will consume an XID.
>
> That makes sense. Thank you very much.
Regards,

Michał Albrycht

In response to

Browse pgsql-general by date

  From Date Subject
Next Message jayesh thakare 2024-11-08 18:12:37 Can we directly upgrade postgresql from 13 to 15.4
Previous Message Tom Lane 2024-11-08 14:39:48 Re: Why plpython functions increase transaction counter much more then plpgsql functions?