On 2016-08-31 06:10:31 +0200, Joel Jacobson wrote: > This is important if you as a caller function want to be sure none of > the work made by anything called down the stack gets committed. > That is, if you as a caller decide to rollback, e.g. by raising an > exception, and you want to be sure *everything* gets rollbacked, > including all work by functions you've called.
> If the caller can't control this, then the author of the caller > function would need to inspect the source code of all function being > called, to be sure there are no code using autonomous transactions. I'm not convinced this makes much sense. All FDWs, dblink etc. already allow you do stuff outside of a transaction. Andres -- Sent via pgsql-hackers mailing list (email@example.com) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers