| From: | Fabien COELHO <coelho(at)cri(dot)ensmp(dot)fr> |
|---|---|
| To: | Craig Ringer <craig(at)2ndquadrant(dot)com> |
| Cc: | Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org>, Fabrízio de Royes Mello <fabriziomello(at)gmail(dot)com>, Joe Conway <mail(at)joeconway(dot)com> |
| Subject: | Re: proposal: session server side variables |
| Date: | 2017-01-04 13:33:25 |
| Message-ID: | alpine.DEB.2.20.1701041423240.22281@lancre |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
> An alternative is to implement sub (nested) transactions, like Oracle
> and MS SQL Server... but that would be quite some work.
As a complement, a search showed that IBM DB2, cited as a reference by
Pavel, has AUTONOMOUS transactions, which looks pretty much the same thing
as nested transactions. The documentation presents an interesting use
security-related use case:
https://www.ibm.com/developerworks/data/library/techarticle/dm-0907autonomoustransactions/
The idea is that an application must record an attempt to access a data
even if the attempt fails and is rolled-back.
This feature used carefully within an appropriate pattern would allow to
ensure that if the setup transaction fails then the session status is
FALSE. One possible inconsistency which may arise with sub xacts is that
the status may stay FALSE while the setup has succeeded, however this on
the safe side wrt to the security use case.
--
Fabien.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Craig Ringer | 2017-01-04 13:37:53 | Re: pg_recvlogical --endpos |
| Previous Message | Mithun Cy | 2017-01-04 11:51:23 | Re: Cache Hash Index meta page. |