| From: | Jim Nasby <Jim(dot)Nasby(at)BlueTreble(dot)com> |
|---|---|
| To: | Josh Berkus <josh(at)agliodbs(dot)com>, Joel Jacobson <joel(at)trustly(dot)com> |
| Cc: | Merlin Moncure <mmoncure(at)gmail(dot)com>, Robert Haas <robertmhaas(at)gmail(dot)com>, Rajeev rastogi <rajeev(dot)rastogi(at)huawei(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>, Simon Riggs <simon(at)2ndquadrant(dot)com> |
| Subject: | Re: Autonomous Transaction is back |
| Date: | 2015-07-27 23:43:47 |
| Message-ID: | 55B6C233.5060606@BlueTreble.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 7/27/15 5:56 PM, Josh Berkus wrote:
> Can you explain what use case you have where simply telling the staff
> "if you use ATX without clearing it, you'll be fired" is not sufficient?
> Possibly there's something we failed to account for in the unconference
> discussion.
That there's no way to enforce that, short of hand-auditing code?
There's already enough things that are difficult/impossible to enforce,
I'd rather not add another one.
--
Jim Nasby, Data Architect, Blue Treble Consulting, Austin TX
Data in Trouble? Get it in Treble! http://BlueTreble.com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Jim Nasby | 2015-07-27 23:47:02 | Re: Autonomous Transaction is back |
| Previous Message | Jim Nasby | 2015-07-27 23:40:42 | Re: Autonomous Transaction is back |