Re: Using transactions with plpythonu - Mailing list pgsql-general

From Tom Lane
Subject Re: Using transactions with plpythonu
Date
Msg-id 27904.1169403694@sss.pgh.pa.us
Whole thread Raw
In response to Re: Using transactions with plpythonu  ("imageguy" <imageguy1206@gmail.com>)
Responses Re: Using transactions with plpythonu  ("imageguy" <imageguy1206@gmail.com>)
List pgsql-general
"imageguy" <imageguy1206@gmail.com> writes:
> So... unless I am missing something, I would suggest you CANNOT us
> plpython (or perhaps any other pl language ??) to process transactions

I think the point you are missing is that every function already runs
within a transaction.  You can't issue BEGIN/COMMIT from within a
function because that would represent destroying the transaction that
supports your execution of the function.

AFAICT you are worried about whether several different updates issued by
your function will all be committed atomically.  They will be; you don't
need to, and indeed can't, do anything to adjust that.  If there was
some other issue you had, you need to be more specific...

            regards, tom lane

pgsql-general by date:

Previous
From: Tom Lane
Date:
Subject: Re: Using transactions with plpythonu
Next
From: Tom Lane
Date:
Subject: Re: More grist for the PostgreSQL vs MySQL mill