From: Konstantin Osipov <kostja@tarantool.org>
To: tarantool-patches@freelists.org
Cc: Georgy Kirichenko <georgy@tarantool.org>
Subject: [tarantool-patches] Re: [PATCH] Do not enable commit if read_only = true
Date: Thu, 28 Feb 2019 13:25:30 +0300 [thread overview]
Message-ID: <20190228102530.GB18858@chai> (raw)
In-Reply-To: <20190227090237.lu32o77lkyllgvui@esperanza>
* Vladimir Davydov <vdavydov.dev@gmail.com> [19/02/27 12:26]:
> On Wed, Feb 27, 2019 at 10:36:00AM +0300, Georgy Kirichenko wrote:
> > Disable commit if server is in read only mode.
>
> The commit message is very poor. Please elaborate why this is important.
Having thought about it we should go over all in-flight
transactions in vinyl and abort them.
We already use this approach on DDL.
We could make it more general.
--
Konstantin Osipov, Moscow, Russia, +7 903 626 22 32
http://tarantool.io - www.twitter.com/kostja_osipov
next prev parent reply other threads:[~2019-02-28 10:25 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-27 7:36 [tarantool-patches] " Georgy Kirichenko
2019-02-27 9:02 ` Vladimir Davydov
2019-02-28 10:25 ` Konstantin Osipov [this message]
2019-03-03 20:49 ` [tarantool-patches] " Георгий Кириченко
2019-03-04 9:41 ` Konstantin Osipov
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=20190228102530.GB18858@chai \
--to=kostja@tarantool.org \
--cc=georgy@tarantool.org \
--cc=tarantool-patches@freelists.org \
--subject='[tarantool-patches] Re: [PATCH] Do not enable commit if read_only = true' \
/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