From: Konstantin Osipov <kostja.osipov@gmail.com>
To: Georgy Kirichenko <georgy@tarantool.org>
Cc: tarantool-patches@dev.tarantool.org
Subject: Re: [Tarantool-patches] [PATCH] Trigger on vclock change
Date: Fri, 15 Nov 2019 16:57:04 +0300 [thread overview]
Message-ID: <20191115135704.GA7713@atlas> (raw)
In-Reply-To: <14579640.zJlKmNO63O@home.lan>
* Georgy Kirichenko <georgy@tarantool.org> [19/11/15 09:43]:
> 90% of tarantool core developers are sitting together in one room or just
> call-available during the day. Also, please, tell us how many RFC responds you
> saw from a somebody who is not a part of tarantool core team. So, you wish to
> force the whole team to use only this inconvenient and unproductive (because
> of long-latency responds) communication way because of your beliefs.
> So I have the another look: each thing to be discussed should be discussed (or
> brainstormed) verbally (because we are the tarantol TEAM members) first and
> only then a well-designed RFC could be formed (or, maybe, you wish to have
> lots of worthless RFCs but I no see any point here).
I gave earlier in this thread concrete examples how active-active
won't work. It didn't take me long. You chose to respond back with
some vague claims and promises of magic.
If you have a miracle design, and you happen to not want to send
an RFC, you still can prove it by sending a patch. Last time it
didn't work: your refused to send an RFC for in-memory WAL - and
the patch can't pass the code review for over 3 months.
All this suggests that the patch by Maria is simply not worth it.
Whatever it is needed for may never happen - and even if it
happens, it is most likely the wrong thing to do.
--
Konstantin Osipov, Moscow, Russia
next prev parent reply other threads:[~2019-11-15 13:57 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-14 12:57 Maria
2019-11-14 13:44 ` Konstantin Osipov
2019-11-14 14:06 ` Georgy Kirichenko
2019-11-14 15:26 ` Konstantin Osipov
2019-11-14 17:13 ` Georgy Kirichenko
2019-11-14 17:33 ` Konstantin Osipov
2019-11-14 19:16 ` Georgy Kirichenko
2019-11-14 19:48 ` Konstantin Osipov
2019-11-14 20:01 ` Georgy Kirichenko
2019-11-15 1:57 ` Konstantin Osipov
2019-11-15 6:02 ` Georgy Kirichenko
2019-11-15 13:57 ` Konstantin Osipov [this message]
2019-11-15 19:57 ` Georgy Kirichenko
2019-11-16 10:37 ` Konstantin Osipov
2019-11-16 20:43 ` Georgy Kirichenko
2019-11-16 11:56 ` Konstantin Osipov
2019-11-16 20:34 ` Georgy Kirichenko
2019-11-18 9:31 ` Konstantin Osipov
2020-06-02 12:22 ` Maria Khaydich
2020-06-03 10:12 ` Sergey Ostanevich
2020-06-03 12:08 ` Alexander Turenko
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=20191115135704.GA7713@atlas \
--to=kostja.osipov@gmail.com \
--cc=georgy@tarantool.org \
--cc=tarantool-patches@dev.tarantool.org \
--subject='Re: [Tarantool-patches] [PATCH] Trigger on vclock change' \
/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