On 30 August 2016 at 23:10, Joel Jacobson <j...@trustly.com> wrote: > > There should be a way to within the session and/or txn permanently > block autonomous transactions. >
This will defeat one of the use cases of autonomous transactions: auditing > > Coding conventions, rules and discipline are all good and will help > against misuse of the feature, but some day someone will make a > mistake and wrongly use the autonomous transaction and cause unwanted > unknown side-effect I as a caller function didn't expect or know > about. > well, if the feature is not guilty why do you want to put it in jail? -- Jaime Casanova www.2ndQuadrant.com PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
