Re: Autonomous Transaction (WIP)
От | Pavan Deolasee |
---|---|
Тема | Re: Autonomous Transaction (WIP) |
Дата | |
Msg-id | CABOikdN-gejf=jyufqz3_Vn8k6yzu9a42A52NXNM=_4vQbX-ng@mail.gmail.com обсуждение исходный текст |
Ответ на | Re: Autonomous Transaction (WIP) (Rajeev rastogi <rajeev.rastogi@huawei.com>) |
Ответы |
Re: Autonomous Transaction (WIP)
Re: Autonomous Transaction (WIP) |
Список | pgsql-hackers |
On Wed, Apr 9, 2014 at 11:03 AM, Rajeev rastogi <rajeev.rastogi@huawei.com> wrote:
Though autonomous transaction uses mixed approach of sub-transaction as well as main
transaction, transaction state of autonomous transaction is handled independently.
Whenever I was asked to have a look at implementing this feature, I always wondered about the great amount of global state that a backend maintains which is normally tied to a single top transaction. Since AT will have same characteristics as a top level transaction, I wonder how do you plan to separate those global state variables ? Sure, we can group them in a structure and 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 going to be tricky.
Thanks,
Pavan
Pavan Deolasee
http://www.linkedin.com/in/pavandeolasee
В списке pgsql-hackers по дате отправления: