On Jan 14, 2009, at 9:41 AM, Wright, George 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?
Yes, they all share the same transaction scope. And PL/pgSQL functions
cannot change the transaction state (i.e. call commit or start a new
transaction).
John DeSoi, Ph.D.
-----------
Then if there is a large amount of code all wrapped by a single
transaction and it hangs somewhere in the code, what technique can be
used to abort the transaction? (It's not really a deadlock)
Thanks.
