<div class="WordSection1"><p class="MsoNormal">On <span style="font-size:10.0pt;font-family:"Tahoma","sans-serif""> 09
April2014 12:14, Pavan Deolasee Wrote:<br /><br /></span><p class="MsoNormal">>Whenever I was asked to have a look
atimplementing this feature, I always wondered about the great amount of global state that a backend maintains which is
normallytied to a single top transaction. Since AT will have same characteristics as a top level transaction, I <p
class="MsoNormal">>wonderhow do you plan to separate those global state variables ? Sure, we can group them in a
structureand put them on a stack when an AT starts and pop them off when the original top transaction becomes active
again,finding all such global state variables is <p class="MsoNormal">>going to be tricky.<p class="MsoNormal"> <p
class="MsoNormal">Icould think of few global variables like transaction properties related(i.e. read-only mode,
isolationlevel etc). As I plan to keep transaction properties of autonomous transaction same as main transaction, so
thereis no need to have these global variables separately. <p class="MsoNormal">Apart from this there are global
variableslike with-in transaction counters, GUC, xactStartTimeStamp. I think there is no need to maintain these
variablesalso separately. They can continue from previous value for autonomous transaction also similar to as
sub-transactiondoes.<p class="MsoNormal"> <p class="MsoNormal">In-case of autonomous transaction, only specific global
variablesinitialized are related to resources (similar to sub-transaction), which anyway gets stored in current
transactionstate.<p class="MsoNormal"> <p class="MsoNormal">Please let me know if I am missing something or if you have
somespecific global variables related issue.<p class="MsoNormal"> <p class="MsoNormal"><i><span
style="color:black">Thanksand Regards,</span></i><p class="MsoNormal"><i>Kumar Rajeev Rastogi<span style="color:black">
</span></i><pclass="MsoNormal"> </div>