From: Aleksandr Lyapunov <alyapunov@tarantool.org> To: tarantool-patches@dev.tarantool.org Subject: [Tarantool-patches] [PATCH v3 06/13] txm: add TX status Date: Wed, 15 Jul 2020 16:55:29 +0300 [thread overview] Message-ID: <1594821336-14468-7-git-send-email-alyapunov@tarantool.org> (raw) In-Reply-To: <1594821336-14468-1-git-send-email-alyapunov@tarantool.org> Transaction engine (see further commits) needs to distinguish and maniputate transactions by their status. The status describe the lifetime point of a transaction (inprogress, prepared, committed) and its abilities (conflicted, read view). Part of #4897 Part of #5108 --- src/box/txn.c | 5 +++++ src/box/txn.h | 36 ++++++++++++++++++++++++++++++++++++ 2 files changed, 41 insertions(+) diff --git a/src/box/txn.c b/src/box/txn.c index 62b91d6..0372047 100644 --- a/src/box/txn.c +++ b/src/box/txn.c @@ -231,6 +231,7 @@ txn_begin(void) txn->flags = 0; txn->in_sub_stmt = 0; txn->id = ++tsn; + txn->status = TXN_INPROGRESS; txn->signature = TXN_SIGNATURE_ROLLBACK; txn->engine = NULL; txn->engine_tx = NULL; @@ -455,6 +456,7 @@ txn_complete(struct txn *txn) * IPROTO_NOP or IPROTO_CONFIRM statements. */ if (txn->signature < 0) { + txn->status = TXN_ABORTED; /* Undo the transaction. */ struct txn_stmt *stmt; stailq_reverse(&txn->stmts); @@ -465,6 +467,7 @@ txn_complete(struct txn *txn) if (txn_has_flag(txn, TXN_HAS_TRIGGERS)) txn_run_rollback_triggers(txn, &txn->on_rollback); } else if (!txn_has_flag(txn, TXN_WAIT_SYNC)) { + txn->status = TXN_COMMITTED; /* Commit the transaction. */ if (txn->engine != NULL) engine_commit(txn->engine, txn); @@ -662,6 +665,7 @@ txn_prepare(struct txn *txn) trigger_clear(&txn->fiber_on_yield); txn->start_tm = ev_monotonic_now(loop()); + txn->status = TXN_PREPARED; return 0; } @@ -895,6 +899,7 @@ void txn_rollback(struct txn *txn) { assert(txn == in_txn()); + txn->status = TXN_ABORTED; trigger_clear(&txn->fiber_on_stop); if (!txn_has_flag(txn, TXN_CAN_YIELD)) trigger_clear(&txn->fiber_on_yield); diff --git a/src/box/txn.h b/src/box/txn.h index 36b1a03..e261852 100644 --- a/src/box/txn.h +++ b/src/box/txn.h @@ -121,6 +121,40 @@ enum { }; /** + * Status of a transaction. + */ +enum txn_status { + /** + * Initial state of TX. The only state of a TX that allowed to do + * read or write actions. + */ + TXN_INPROGRESS, + /** + * The TX have passed conflict checks and is ready to be committed. + */ + TXN_PREPARED, + /** + * The TX was aborted when other TX was committed due to conflict. + */ + TXN_CONFLICTED, + /** + * The TX was read_only, has a conflict and was sent to read view. + * Read-only and does not participate in conflict resolution ever more. + * This transaction can onlu see state of the database at some fixed + * point in the past. + */ + TXN_IN_READ_VIEW, + /** + * The TX was committed. + */ + TXN_COMMITTED, + /** + * The TX was aborted by user. + */ + TXN_ABORTED, +}; + +/** * A single statement of a multi-statement * transaction: undo and redo info. */ @@ -217,6 +251,8 @@ struct txn { * Valid IDs start from 1. */ int64_t id; + /** Status of the TX */ + enum txn_status status; /** List of statements in a transaction. */ struct stailq stmts; /** Number of new rows without an assigned LSN. */ -- 2.7.4
next prev parent reply other threads:[~2020-07-15 13:55 UTC|newest] Thread overview: 41+ messages / expand[flat|nested] mbox.gz Atom feed top 2020-07-15 13:55 [Tarantool-patches] [PATCH v3 00/13] Transaction engine for memtx engine Aleksandr Lyapunov 2020-07-15 13:55 ` [Tarantool-patches] [PATCH v3 01/13] Update license file (2020) Aleksandr Lyapunov 2020-07-15 13:55 ` [Tarantool-patches] [PATCH v3 02/13] Check data_offset overflow in struct tuple Aleksandr Lyapunov 2020-07-16 14:27 ` Nikita Pettik 2020-07-15 13:55 ` [Tarantool-patches] [PATCH v3 03/13] vinyl: rename tx_manager -> vy_tx_manager Aleksandr Lyapunov 2020-07-15 16:04 ` Nikita Pettik 2020-07-16 8:17 ` Aleksandr Lyapunov 2020-07-15 13:55 ` [Tarantool-patches] [PATCH v3 04/13] txm: introduce dirty tuples Aleksandr Lyapunov 2020-07-15 16:22 ` Nikita Pettik 2020-07-16 0:05 ` Vladislav Shpilevoy 2020-07-15 13:55 ` [Tarantool-patches] [PATCH v3 05/13] txm: save txn in txn_stmt Aleksandr Lyapunov 2020-07-15 16:23 ` Nikita Pettik 2020-07-15 13:55 ` Aleksandr Lyapunov [this message] 2020-07-15 16:42 ` [Tarantool-patches] [PATCH v3 06/13] txm: add TX status Nikita Pettik 2020-07-16 0:08 ` Vladislav Shpilevoy 2020-07-15 13:55 ` [Tarantool-patches] [PATCH v3 07/13] txm: save does_require_old_tuple flag in txn_stmt Aleksandr Lyapunov 2020-07-15 16:49 ` Nikita Pettik 2020-07-16 0:09 ` Vladislav Shpilevoy 2020-07-15 13:55 ` [Tarantool-patches] [PATCH v3 08/13] txm: introduce tx manager Aleksandr Lyapunov 2020-07-15 16:51 ` Nikita Pettik 2020-07-15 22:01 ` Vladislav Shpilevoy 2020-07-16 0:10 ` Vladislav Shpilevoy 2020-07-15 13:55 ` [Tarantool-patches] [PATCH v3 09/13] tmx: introduce prepare sequence number Aleksandr Lyapunov 2020-07-15 17:13 ` Nikita Pettik 2020-07-16 0:11 ` Vladislav Shpilevoy 2020-07-15 13:55 ` [Tarantool-patches] [PATCH v3 10/13] tmx: introduce conflict tracker Aleksandr Lyapunov 2020-07-16 0:16 ` Vladislav Shpilevoy 2020-07-15 13:55 ` [Tarantool-patches] [PATCH v3 11/13] txm: introduce txm_story Aleksandr Lyapunov 2020-07-16 0:20 ` Vladislav Shpilevoy 2020-07-17 6:16 ` Aleksandr Lyapunov 2020-07-16 22:25 ` Vladislav Shpilevoy 2020-07-15 13:55 ` [Tarantool-patches] [PATCH v3 12/13] txm: clarify all fetched tuples Aleksandr Lyapunov 2020-07-15 13:55 ` [Tarantool-patches] [PATCH v3 13/13] tmx: use new tx manager in memtx Aleksandr Lyapunov 2020-07-16 22:26 ` Vladislav Shpilevoy 2020-07-17 5:08 ` Aleksandr Lyapunov 2020-07-23 20:58 ` Vladislav Shpilevoy 2020-07-15 15:47 ` [Tarantool-patches] [PATCH v3 00/13] Transaction engine for memtx engine Aleksandr Lyapunov 2020-07-15 16:38 ` Aleksandr Lyapunov 2020-07-15 16:39 ` Aleksandr Lyapunov 2020-07-15 16:40 ` Aleksandr Lyapunov 2020-07-16 0:05 ` Vladislav Shpilevoy
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=1594821336-14468-7-git-send-email-alyapunov@tarantool.org \ --to=alyapunov@tarantool.org \ --cc=tarantool-patches@dev.tarantool.org \ --subject='Re: [Tarantool-patches] [PATCH v3 06/13] txm: add TX status' \ /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