Re: function transaction scope question - Mailing list pgsql-novice

From Christopher Browne
Subject Re: function transaction scope question
Date
Msg-id d6d6637f0901140747t90b4d00q2b35af813d3ebc9@mail.gmail.com
Whole thread Raw
In response to function transaction scope question  ("Wright, George" <George.Wright@infimatic.com>)
Responses another transaction question  ("Wright, George" <George.Wright@infimatic.com>)
List pgsql-novice
On Wed, Jan 14, 2009 at 9:41 AM, Wright, George
<George.Wright@infimatic.com> wrote:
> If a function in PL/pgSQL is wrapped by a transaction, does that same single
> transaction encompass other functions defined elsewhere that this function
> calls?

There's a rather stronger condition than that to be claimed...

*EVERY* PostgreSQL stored function call (irrespective of language)
runs within the context of a particular transaction.  That transaction
context will therefore include all of the following:
 - any functions that the stored function may call
 - any triggers that may be fired by virtue of table updates
 - invocation of NOTIFY (but *not* the notifications that result in
listening connections)

That's quite comfortably stronger than what you appear to be hoping for :-).
--
http://linuxfinances.info/info/linuxdistributions.html
Steve Martin  - "I like a woman with a head on her shoulders. I hate necks."

pgsql-novice by date:

Previous
From: "Wright, George"
Date:
Subject: function transaction scope question
Next
From: "Wright, George"
Date:
Subject: another transaction question