[tarantool-patches] [PATCH] txn: don't unref stmt tuples before rollback triggers are run
Vladimir Davydov
vdavydov.dev at gmail.com
Wed Jul 24 15:55:18 MSK 2019
On Wed, Jul 24, 2019 at 03:30:47PM +0300, Георгий Кириченко wrote:
> Could we consider the possibility to assign triggers on a statement itself?
> In this case you shouldn't implement all that machinery with savepoints.
FYI I scrapped this patch, as I wrote in reply to this email:
https://www.freelists.org/post/tarantool-patches/PATCH-txn-dont-unref-stmt-tuples-before-rollback-triggers-are-run,1
Instead I made savepoints support commit/rollback triggers:
https://www.freelists.org/post/tarantool-patches/PATCH-04-Support-savepoints-in-DDL-transactions
Regarding assigning commit/rollback triggers to individual statements.
Although this would indeed work, I prefer not to do that, because it's
somewhat expensive from the memory usage pov. Besides splitting
commit/rollback trigger lists like that would complicate the code
involving the triggers (running, setting/clearing triggers from Lua).
More information about the Tarantool-patches
mailing list