Re: Why plpython functions increase transaction counter much more then plpgsql functions? - Mailing list pgsql-general

From Michał Albrycht
Subject Re: Why plpython functions increase transaction counter much more then plpgsql functions?
Date
Msg-id CACsoHGCsXBYbv__t2xDVxth1EroBTsO=SnfJror4HCy-XtN4Lg@mail.gmail.com
Whole thread Raw
In response to Re: Why plpython functions increase transaction counter much more then plpgsql functions?  (Tom Lane <tgl@sss.pgh.pa.us>)
List 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 

pgsql-general by date:

Previous
From: Tom Lane
Date:
Subject: Re: Why plpython functions increase transaction counter much more then plpgsql functions?
Next
From: jayesh thakare
Date:
Subject: Can we directly upgrade postgresql from 13 to 15.4