Re: Autonomous Transaction (WIP)
От | Tom Lane |
---|---|
Тема | Re: Autonomous Transaction (WIP) |
Дата | |
Msg-id | 26692.1396988001@sss.pgh.pa.us обсуждение исходный текст |
Ответ на | Re: Autonomous Transaction (WIP) (Robert Haas <robertmhaas@gmail.com>) |
Ответы |
Re: Autonomous Transaction (WIP)
Re: Autonomous Transaction (WIP) |
Список | pgsql-hackers |
Robert Haas <robertmhaas@gmail.com> writes: > I'm also pretty unconvinced that multiple PGPROCs is the right way to > go. First, PGPROCs have a bunch of state in them that is assumed to > exist once per backend. We might find pretty substantial code churn > there if we try to go change that. Second, why do other backends > really need to know about our ATs? As far as I can see, if other > backends see the AT as a subtransaction of our top-level transaction > up until it actually commits, that ought to be just fine. If we can make it work like that, sure. I'm a bit worried about how you'd decouple a subtransaction and commit it atomically ... or if that's not atomic, will it create any problems? The point being that you need to change both pg_subtrans and pg_clog to make that state transition. regards, tom lane
В списке pgsql-hackers по дате отправления: