From: Aleksandr Lyapunov <alyapunov@tarantool.org> To: tarantool-patches@dev.tarantool.org Cc: v.shpilevoy@tarantool.org Subject: [Tarantool-patches] [PATCH 06/16] tx: add TX status Date: Wed, 8 Jul 2020 18:14:13 +0300 [thread overview] Message-ID: <1594221263-6228-7-git-send-email-alyapunov@tarantool.org> (raw) In-Reply-To: <1594221263-6228-1-git-send-email-alyapunov@tarantool.org> --- src/box/txn.c | 5 +++++ src/box/txn.h | 34 ++++++++++++++++++++++++++++++++++ 2 files changed, 39 insertions(+) diff --git a/src/box/txn.c b/src/box/txn.c index 22013cc..b26613c 100644 --- a/src/box/txn.c +++ b/src/box/txn.c @@ -223,6 +223,7 @@ txn_begin(void) txn->flags = 0; txn->in_sub_stmt = 0; txn->id = ++tsn; + txn->status = TXN_INPROGRESS; txn->signature = -1; txn->engine = NULL; txn->engine_tx = NULL; @@ -426,6 +427,7 @@ txn_complete(struct txn *txn) * IPROTO_NOP statements only. */ if (txn->signature < 0) { + txn->status = TXN_ABORTED; /* Undo the transaction. */ struct txn_stmt *stmt; stailq_reverse(&txn->stmts); @@ -436,6 +438,7 @@ txn_complete(struct txn *txn) if (txn_has_flag(txn, TXN_HAS_TRIGGERS)) txn_run_rollback_triggers(txn, &txn->on_rollback); } else { + txn->status = TXN_COMMITTED; /* Commit the transaction. */ if (txn->engine != NULL) engine_commit(txn->engine, txn); @@ -580,6 +583,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; } @@ -708,6 +712,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 5b264f0..1394bfb 100644 --- a/src/box/txn.h +++ b/src/box/txn.h @@ -77,6 +77,38 @@ 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 by other TX 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. + */ + TXN_IN_READ_VIEW, + /** + * The TX was committed. + */ + TXN_COMMITTED, + /** + * The TX was aborted. + */ + TXN_ABORTED, +}; + +/** * A single statement of a multi-statement * transaction: undo and redo info. */ @@ -173,6 +205,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-08 15:14 UTC|newest] Thread overview: 49+ messages / expand[flat|nested] mbox.gz Atom feed top 2020-07-08 15:14 [Tarantool-patches] [PATCH v2 00/16] Transaction engine for memtx engine Aleksandr Lyapunov 2020-07-08 15:14 ` [Tarantool-patches] [PATCH 01/16] Update license file (2020) Aleksandr Lyapunov 2020-07-08 15:14 ` [Tarantool-patches] [PATCH 02/16] Check data_offset overflow in struct tuple Aleksandr Lyapunov 2020-07-12 17:15 ` Vladislav Shpilevoy 2020-07-14 17:09 ` Aleksandr Lyapunov 2020-07-14 22:48 ` Vladislav Shpilevoy 2020-07-08 15:14 ` [Tarantool-patches] [PATCH 03/16] tx: introduce dirty tuples Aleksandr Lyapunov 2020-07-12 17:15 ` Vladislav Shpilevoy 2020-07-12 22:24 ` Nikita Pettik 2020-07-08 15:14 ` [Tarantool-patches] [PATCH 04/16] vinyl: rename tx_manager -> vy_tx_manager Aleksandr Lyapunov 2020-07-12 17:14 ` Vladislav Shpilevoy 2020-07-08 15:14 ` [Tarantool-patches] [PATCH 05/16] tx: save txn in txn_stmt Aleksandr Lyapunov 2020-07-12 17:15 ` Vladislav Shpilevoy 2020-07-08 15:14 ` Aleksandr Lyapunov [this message] 2020-07-12 17:15 ` [Tarantool-patches] [PATCH 06/16] tx: add TX status Vladislav Shpilevoy 2020-07-08 15:14 ` [Tarantool-patches] [PATCH 07/16] tx: save preserve old tuple flag in txn_stmt Aleksandr Lyapunov 2020-07-12 17:14 ` Vladislav Shpilevoy 2020-07-14 23:46 ` Vladislav Shpilevoy 2020-07-15 7:53 ` Aleksandr Lyapunov 2020-07-08 15:14 ` [Tarantool-patches] [PATCH 08/16] tx: introduce tx manager Aleksandr Lyapunov 2020-07-08 15:14 ` [Tarantool-patches] [PATCH 09/16] tx: introduce prepare sequence number Aleksandr Lyapunov 2020-07-08 15:14 ` [Tarantool-patches] [PATCH 10/16] tx: introduce txn_stmt_destroy Aleksandr Lyapunov 2020-07-12 17:15 ` Vladislav Shpilevoy 2020-07-08 15:14 ` [Tarantool-patches] [PATCH 11/16] tx: introduce conflict tracker Aleksandr Lyapunov 2020-07-12 17:15 ` Vladislav Shpilevoy 2020-07-14 23:51 ` Vladislav Shpilevoy 2020-07-15 7:57 ` Aleksandr Lyapunov 2020-07-08 15:14 ` [Tarantool-patches] [PATCH 12/16] introduce tuple smart pointers Aleksandr Lyapunov 2020-07-12 17:16 ` Vladislav Shpilevoy 2020-07-08 15:14 ` [Tarantool-patches] [PATCH 13/16] tx: introduce txm_story Aleksandr Lyapunov 2020-07-12 17:14 ` Vladislav Shpilevoy 2020-07-14 23:46 ` Vladislav Shpilevoy 2020-07-15 8:11 ` Aleksandr Lyapunov 2020-07-15 22:02 ` Vladislav Shpilevoy 2020-07-08 15:14 ` [Tarantool-patches] [PATCH 14/16] tx: indexes Aleksandr Lyapunov 2020-07-14 23:50 ` Vladislav Shpilevoy 2020-07-15 10:02 ` Aleksandr Lyapunov 2020-07-15 22:08 ` Vladislav Shpilevoy 2020-07-15 10:19 ` Aleksandr Lyapunov 2020-07-08 15:14 ` [Tarantool-patches] [PATCH 15/16] tx: introduce point conflict tracker Aleksandr Lyapunov 2020-07-08 15:14 ` [Tarantool-patches] [PATCH 16/16] tx: use new tx manager in memtx Aleksandr Lyapunov 2020-07-14 23:45 ` Vladislav Shpilevoy 2020-07-15 10:32 ` Aleksandr Lyapunov 2020-07-15 22:09 ` Vladislav Shpilevoy 2020-07-12 17:19 ` [Tarantool-patches] [PATCH v2 00/16] Transaction engine for memtx engine Vladislav Shpilevoy 2020-07-14 23:47 ` Vladislav Shpilevoy 2020-07-15 12:25 ` Aleksandr Lyapunov 2020-07-15 22:10 ` Vladislav Shpilevoy 2020-07-16 4:48 ` 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=1594221263-6228-7-git-send-email-alyapunov@tarantool.org \ --to=alyapunov@tarantool.org \ --cc=tarantool-patches@dev.tarantool.org \ --cc=v.shpilevoy@tarantool.org \ --subject='Re: [Tarantool-patches] [PATCH 06/16] tx: 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