Re: [HACKERS] Transaction control in procedures
От | Peter Eisentraut |
---|---|
Тема | Re: [HACKERS] Transaction control in procedures |
Дата | |
Msg-id | 20c89ac4-fcde-caa6-1503-7ee075a1caf2@2ndquadrant.com обсуждение исходный текст |
Ответ на | [HACKERS] Transaction control in procedures (Peter Eisentraut <peter.eisentraut@2ndquadrant.com>) |
Ответы |
Re: [HACKERS] Transaction control in procedures
|
Список | pgsql-hackers |
On 10/31/17 15:38, Peter Eisentraut wrote: > Here is a patch that implements transaction control in PL/Python > procedures. (This patch goes on top of "SQL procedures" patch v1.) Here is an updated patch, now on top of "SQL procedures" v2. Relative to the previous patch v1 I added transaction control to PL/pgSQL, PL/Perl, and PL/Tcl with relative ease. (There is a weird crash in one PL/Perl test that is currently commented out. And I can't get a proper backtrace. Maybe something to do with recursive Perl interpreters?) I crash-coursed myself in PL/Perl and PL/Tcl (and Tcl). If anyone has more of a feel for those languages and wants to comment on the proposed interfaces and internals, please chime in. I also added tracking so that transaction control commands can only be made in the proper context, currently meaning only top-level procedure calls, not functions or other procedure calls. This should be extended to also allow nested CALLs without anything in between, but I need more time to code that. I'll spend a bit more time on tidying up a few things, and a bunch of documentation is missing, but I currently don't see any more major issues here. -- Peter Eisentraut http://www.2ndQuadrant.com/ PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
Вложения
В списке pgsql-hackers по дате отправления: