From: Aleksandr Lyapunov <alyapunov@tarantool.org> To: tarantool-patches@dev.tarantool.org Subject: [Tarantool-patches] [PATCH 07/15] tx: save preserve old tuple flag in txn_stmt Date: Fri, 3 Jul 2020 09:33:09 +0300 [thread overview] Message-ID: <1593757997-4145-8-git-send-email-alyapunov@tarantool.org> (raw) In-Reply-To: <1593757997-4145-1-git-send-email-alyapunov@tarantool.org> --- src/box/memtx_space.c | 17 +++++++++++++++++ src/box/txn.c | 3 +++ src/box/txn.h | 9 +++++++++ 3 files changed, 29 insertions(+) diff --git a/src/box/memtx_space.c b/src/box/memtx_space.c index 8755920..5820c40 100644 --- a/src/box/memtx_space.c +++ b/src/box/memtx_space.c @@ -316,6 +316,10 @@ memtx_space_execute_replace(struct space *space, struct txn *txn, if (stmt->new_tuple == NULL) return -1; tuple_ref(stmt->new_tuple); + + if (mode == DUP_INSERT) + stmt->preserve_old_tuple = true; + if (memtx_space->replace(space, NULL, stmt->new_tuple, mode, &stmt->old_tuple) != 0) return -1; @@ -342,6 +346,13 @@ memtx_space_execute_delete(struct space *space, struct txn *txn, struct tuple *old_tuple; if (index_get(pk, key, part_count, &old_tuple) != 0) return -1; + + /* + * We have to delete exactly old_tuple just because we return it as + * a result. + */ + stmt->preserve_old_tuple = true; + if (old_tuple != NULL && memtx_space->replace(space, old_tuple, NULL, DUP_REPLACE_OR_INSERT, &stmt->old_tuple) != 0) @@ -390,6 +401,9 @@ memtx_space_execute_update(struct space *space, struct txn *txn, if (stmt->new_tuple == NULL) return -1; tuple_ref(stmt->new_tuple); + + stmt->preserve_old_tuple = true; + if (memtx_space->replace(space, old_tuple, stmt->new_tuple, DUP_REPLACE, &stmt->old_tuple) != 0) return -1; @@ -496,6 +510,9 @@ memtx_space_execute_upsert(struct space *space, struct txn *txn, stmt->new_tuple = NULL; } } + + stmt->preserve_old_tuple = true; + /* * It's OK to use DUP_REPLACE_OR_INSERT: we don't risk * inserting a new tuple if the old one exists, since diff --git a/src/box/txn.c b/src/box/txn.c index cf60d54..d1182aa 100644 --- a/src/box/txn.c +++ b/src/box/txn.c @@ -107,6 +107,7 @@ txn_stmt_new(struct region *region) stmt->engine_savepoint = NULL; stmt->row = NULL; stmt->has_triggers = false; + stmt->preserve_old_tuple = false; return stmt; } @@ -349,6 +350,8 @@ txn_commit_stmt(struct txn *txn, struct request *request) */ if (stmt->space != NULL && !rlist_empty(&stmt->space->on_replace) && stmt->space->run_triggers && (stmt->old_tuple || stmt->new_tuple)) { + /* Triggers see old_tuple and that tuple must remain the same */ + stmt->preserve_old_tuple = true; int rc = 0; if(!space_is_temporary(stmt->space)) { rc = trigger_run(&stmt->space->on_replace, txn); diff --git a/src/box/txn.h b/src/box/txn.h index 1394bfb..e860e1e 100644 --- a/src/box/txn.h +++ b/src/box/txn.h @@ -129,6 +129,15 @@ struct txn_stmt { struct xrow_header *row; /** on_commit and/or on_rollback list is not empty. */ bool has_triggers; + /** + * Whether the stmt upon commit must replace exactly old_tuple from it. + * Explanation: to the moment of commit of the statement actual state + * of the space could change due to commit of other transaction(s). + * Some statements require the replaced tuple at the moment of commit to + * be exactly the same as replaced tuple at the moment of execution. + * Some - doesn't. + */ + bool preserve_old_tuple; /** Commit/rollback triggers associated with this statement. */ struct rlist on_commit; struct rlist on_rollback; -- 2.7.4
next prev parent reply other threads:[~2020-07-03 6:33 UTC|newest] Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top 2020-07-03 6:33 [Tarantool-patches] [PATCH 00/15] Transaction engine for memtx engine Aleksandr Lyapunov 2020-07-03 6:33 ` [Tarantool-patches] [PATCH 01/15] Update license file (2020) Aleksandr Lyapunov 2020-07-03 6:33 ` [Tarantool-patches] [PATCH 02/15] Check data_offset overflow in struct tuple Aleksandr Lyapunov 2020-07-05 17:03 ` Vladislav Shpilevoy 2020-07-06 13:39 ` Aleksandr Lyapunov 2020-07-03 6:33 ` [Tarantool-patches] [PATCH 03/15] tx: introduce dirty tuples Aleksandr Lyapunov 2020-07-05 17:04 ` Vladislav Shpilevoy 2020-07-03 6:33 ` [Tarantool-patches] [PATCH 04/15] vinyl: rename tx_manager -> vy_tx_manager Aleksandr Lyapunov 2020-07-05 17:04 ` Vladislav Shpilevoy 2020-07-03 6:33 ` [Tarantool-patches] [PATCH 05/15] tx: save txn in txn_stmt Aleksandr Lyapunov 2020-07-05 17:04 ` Vladislav Shpilevoy 2020-07-03 6:33 ` [Tarantool-patches] [PATCH 06/15] tx: add TX status Aleksandr Lyapunov 2020-07-05 17:04 ` Vladislav Shpilevoy 2020-07-03 6:33 ` Aleksandr Lyapunov [this message] 2020-07-05 17:05 ` [Tarantool-patches] [PATCH 07/15] tx: save preserve old tuple flag in txn_stmt Vladislav Shpilevoy 2020-07-03 6:33 ` [Tarantool-patches] [PATCH 08/15] tx: introduce tx manager Aleksandr Lyapunov 2020-07-03 6:33 ` [Tarantool-patches] [PATCH 09/15] tx: introduce prepare sequence number Aleksandr Lyapunov 2020-07-05 17:05 ` Vladislav Shpilevoy 2020-07-06 13:50 ` Aleksandr Lyapunov 2020-07-03 6:33 ` [Tarantool-patches] [PATCH 10/15] tx: introduce txn_stmt_destroy Aleksandr Lyapunov 2020-07-03 6:33 ` [Tarantool-patches] [PATCH 11/15] tx: introduce conflict tracker Aleksandr Lyapunov 2020-07-03 6:33 ` [Tarantool-patches] [PATCH 12/15] tx: introduce txm_story Aleksandr Lyapunov 2020-07-03 6:33 ` [Tarantool-patches] [PATCH 13/15] tx: indexes Aleksandr Lyapunov 2020-07-03 6:33 ` [Tarantool-patches] [PATCH 14/15] tx: introduce point conflict tracker Aleksandr Lyapunov 2020-07-03 6:33 ` [Tarantool-patches] [PATCH 15/15] tx: use new tx managet in memtx Aleksandr Lyapunov 2020-07-05 17:03 ` [Tarantool-patches] [PATCH 00/15] Transaction engine for memtx engine Vladislav Shpilevoy 2020-07-06 13:29 ` Aleksandr Lyapunov
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=1593757997-4145-8-git-send-email-alyapunov@tarantool.org \ --to=alyapunov@tarantool.org \ --cc=tarantool-patches@dev.tarantool.org \ --subject='Re: [Tarantool-patches] [PATCH 07/15] tx: save preserve old tuple flag in txn_stmt' \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: link
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox