From: Aleksandr Lyapunov <alyapunov@tarantool.org> To: Vladislav Shpilevoy <v.shpilevoy@tarantool.org>, tarantool-patches@dev.tarantool.org Subject: Re: [Tarantool-patches] [PATCH 13/16] tx: introduce txm_story Date: Wed, 15 Jul 2020 11:11:06 +0300 [thread overview] Message-ID: <340f6b5a-4c5d-6d26-1268-da9a7d995ac5@tarantool.org> (raw) In-Reply-To: <85786cb3-af03-03da-0405-b137a17ce929@tarantool.org> Hi, thank for review! On 15.07.2020 02:46, Vladislav Shpilevoy wrote: > Thanks for the patch! > > See 3 comments below. > > > 1. What if index count of the space will change in a concurrect > DDL transaction? That's a good question. I know what should be - DDL must create a new space structure for new transaction while leaving old space structure for old transactions.. But I'm sure it does not work that way now. I'll write a test and file a ticket. > >> +} >> + >> +static struct txm_story * >> +txm_story_new_add_stmt(struct tuple *tuple, struct txn_stmt *stmt) > 2. Probably would be better to use the existing terms: old_tuple and new_tuple. > So the functions would be txm_story_add_new_stmt and txm_story_add_old_stmt. The > same in all the other places. 'add_stmt' -> 'new_stmt'. 'del_stmt' -> 'old_stmt'. I thought about it. I fear in terms of txm_story, when we speak about lifetime of a tuple it would be weird. add_stmt - is the statement that added the tuple. But what is new_stmt? new_psn? > >> +{ >> + struct txm_story *res = txm_story_new(tuple, stmt->space->index_count); >> + if (res == NULL) >> + return NULL; >> + res->add_stmt = stmt; >> + assert(stmt->add_story == NULL); >> + stmt->add_story = res; >> + return res; >> +} >> + >> +static struct txm_story * >> +txm_story_new_del_stmt(struct tuple *tuple, struct txn_stmt *stmt) >> +{ >> + struct txm_story *res = txm_story_new(tuple, stmt->space->index_count); >> + if (res == NULL) >> + return NULL; >> + res->del_stmt = stmt; >> + assert(stmt->del_story == NULL); >> + stmt->del_story = res; >> + return res; >> +} >> + >> +void >> +txm_history_prepare_stmt(struct txn_stmt *stmt) >> +{ >> + assert(stmt->txn->psn != 0); >> + >> + /* Move story to the past to prepared stories. */ >> + >> + struct txm_story *story = stmt->add_story; >> + uint32_t index_count = story == NULL ? 0 : story->index_count; >> + for (uint32_t i = 0; i < index_count; ) { >> ... >> ... >> ... >> + } >> + if (stmt->add_story != NULL) > 3. According to a check in the beginning of the function stmt can > be NULL. But then this will crash. No, index_count is initialized as 0 in that case and we will not enter the loop.
next prev parent reply other threads:[~2020-07-15 8:11 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 ` [Tarantool-patches] [PATCH 06/16] tx: add TX status Aleksandr Lyapunov 2020-07-12 17:15 ` 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 [this message] 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=340f6b5a-4c5d-6d26-1268-da9a7d995ac5@tarantool.org \ --to=alyapunov@tarantool.org \ --cc=tarantool-patches@dev.tarantool.org \ --cc=v.shpilevoy@tarantool.org \ --subject='Re: [Tarantool-patches] [PATCH 13/16] tx: introduce txm_story' \ /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