Peter Eisentraut
d92bc83c48
PL/pgSQL: Nested CALL with transactions
...
So far, a nested CALL or DO in PL/pgSQL would not establish a context
where transaction control statements were allowed. This fixes that by
handling CALL and DO specially in PL/pgSQL, passing the atomic/nonatomic
execution context through and doing the required management around
transaction boundaries.
Reviewed-by: Tomas Vondra <tomas.vondra@2ndquadrant.com >
2018-03-28 13:31:27 -04:00
..
2018-03-28 17:42:50 +01:00
2018-01-02 23:30:12 -05:00
2018-03-27 19:07:39 -07:00
2018-03-23 10:48:22 -03:00
2018-03-15 10:02:59 -03:00
2018-01-02 23:30:12 -05:00
2018-03-28 13:31:27 -04:00
2018-03-22 17:42:03 +03:00
2018-01-02 23:30:12 -05:00
2018-03-27 21:03:10 -07:00
2018-03-01 16:25:46 -08:00
2018-03-17 08:28:51 -04:00
2018-01-02 23:30:12 -05:00
2018-03-27 16:46:51 -04:00
2018-03-22 12:49:48 -04:00
2018-02-19 17:40:00 -03:00
2018-01-09 18:33:21 -05:00
2018-01-02 23:30:12 -05:00
2018-03-15 11:41:42 -04:00
2018-01-02 23:30:12 -05:00
2018-03-21 09:15:04 -04:00
2018-01-02 23:30:12 -05:00
2018-01-02 23:30:12 -05:00
2018-01-02 23:30:12 -05:00
2018-03-27 16:14:40 +03:00
2018-03-28 13:31:27 -04:00
2018-01-02 23:30:12 -05:00
2018-03-27 16:46:51 -04:00
2012-10-07 21:52:43 -04:00
2018-03-23 10:31:10 -04:00
2018-03-22 14:45:59 -07:00
2018-03-14 12:07:28 -04:00
2018-01-02 23:30:12 -05:00
2018-01-02 23:30:12 -05:00
2017-06-08 11:29:50 -04:00
2018-02-09 15:54:45 -05:00
2012-10-07 21:52:43 -04:00
2012-10-07 21:52:43 -04:00
2018-01-02 23:30:12 -05:00
2018-03-21 07:45:15 -04:00
2018-03-22 20:42:25 -04:00
2018-01-02 23:30:12 -05:00
2018-01-02 23:30:12 -05:00
2018-02-02 13:32:44 -05:00
2018-01-02 23:30:12 -05:00
2018-01-02 23:30:12 -05:00
2018-01-02 23:30:12 -05:00
2017-06-21 15:19:25 -04:00
2018-01-02 23:30:12 -05:00
2018-02-14 19:43:33 -05:00
2018-01-02 23:30:12 -05:00
2018-01-02 23:30:12 -05:00