From: Vladislav Shpilevoy <v.shpilevoy@tarantool.org>
To: Serge Petrenko <sergepetrenko@tarantool.org>,
Cyrill Gorcunov <gorcunov@gmail.com>
Cc: tml <tarantool-patches@dev.tarantool.org>
Subject: Re: [Tarantool-patches] [PATCH v9 5/7] applier: process synchro requests without txn engine
Date: Fri, 21 Aug 2020 23:59:44 +0200 [thread overview]
Message-ID: <c3557af3-1d2e-28af-b448-344804d1bc2b@tarantool.org> (raw)
In-Reply-To: <1597999873.222856578@f425.i.mail.ru>
Hi! Thanks for the review!
> diff --git a/src/box/applier.cc b/src/box/applier.cc
> index 1387d518c..c1d07ca54 100644
> --- a/src/box/applier.cc
> +++ b/src/box/applier.cc
> @@ -847,13 +923,26 @@ applier_apply_tx(struct stailq *rows)
> }
> }
>
> + if (unlikely(iproto_type_is_synchro_request(first_row->type))) {
> + /*
> + * Synchro messages are not transactions, in terms
> + * of DML. Always sent and written isolated from
> + * each other.
> + */
> + assert(first_row == last_row);
> + if (apply_synchro_row(first_row) != 0)
> + diag_raise();
> + goto success;
> + }
> +
> /**
> * Explicitly begin the transaction so that we can
> * control fiber->gc life cycle and, in case of apply
> * conflict safely access failed xrow object and allocate
> * IPROTO_NOP on gc.
> */
> - struct txn *txn = txn_begin();
> + struct txn *txn;
> + txn = txn_begin();
>
>
> Why this change?
In C++ you can't declare and assign variables bypassing labels (at
least in clang). It won't compile. Here a new label is added -
'success:'.
But it appeared, that it still allows to declare a variable and
assign it on a next line. So here it is done.
next prev parent reply other threads:[~2020-08-21 21:59 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-19 21:34 [Tarantool-patches] [PATCH v9 0/7] qsync: write CONFIRM/ROLLBACK " Cyrill Gorcunov
2020-08-19 21:34 ` [Tarantool-patches] [PATCH v9 1/7] journal: bind asynchronous write completion to an entry Cyrill Gorcunov
2020-08-21 7:48 ` Serge Petrenko
2020-08-19 21:34 ` [Tarantool-patches] [PATCH v9 2/7] journal: add journal_entry_create helper Cyrill Gorcunov
2020-08-21 7:51 ` Serge Petrenko
2020-08-19 21:34 ` [Tarantool-patches] [PATCH v9 3/7] qsync: provide a binary form of syncro entries Cyrill Gorcunov
2020-08-21 8:15 ` Serge Petrenko
2020-08-19 21:34 ` [Tarantool-patches] [PATCH v9 4/7] qsync: direct write of CONFIRM/ROLLBACK into a journal Cyrill Gorcunov
2020-08-19 22:43 ` Vladislav Shpilevoy
2020-08-20 7:13 ` Cyrill Gorcunov
2020-08-21 8:36 ` Serge Petrenko
2020-08-19 21:34 ` [Tarantool-patches] [PATCH v9 5/7] applier: process synchro requests without txn engine Cyrill Gorcunov
2020-08-21 8:51 ` Serge Petrenko
2020-08-21 21:59 ` Vladislav Shpilevoy [this message]
2020-08-23 12:15 ` Serge Petrenko
2020-08-19 21:34 ` [Tarantool-patches] [PATCH v9 6/7] txn: txn_add_redo -- drop synchro processing Cyrill Gorcunov
2020-08-21 8:52 ` Serge Petrenko
2020-08-19 21:34 ` [Tarantool-patches] [PATCH v9 7/7] xrow: drop xrow_header_dup_body Cyrill Gorcunov
2020-08-21 8:57 ` Serge Petrenko
2020-08-24 21:16 ` [Tarantool-patches] [PATCH v9 0/7] qsync: write CONFIRM/ROLLBACK without txn engine 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=c3557af3-1d2e-28af-b448-344804d1bc2b@tarantool.org \
--to=v.shpilevoy@tarantool.org \
--cc=gorcunov@gmail.com \
--cc=sergepetrenko@tarantool.org \
--cc=tarantool-patches@dev.tarantool.org \
--subject='Re: [Tarantool-patches] [PATCH v9 5/7] applier: process synchro requests without txn engine' \
/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