From: Vladimir Davydov <vdavydov.dev@gmail.com>
To: Konstantin Osipov <kostja@tarantool.org>
Cc: tarantool-patches@freelists.org
Subject: Re: [PATCH] memtx: don't delay deletion of temporary tuples during snapshot
Date: Thu, 14 Jun 2018 11:23:05 +0300 [thread overview]
Message-ID: <20180614082305.padi2xm4czewblwo@esperanza> (raw)
In-Reply-To: <20180608063915.6r6rzuutlr4cpob5@esperanza>
On Fri, Jun 08, 2018 at 09:39:15AM +0300, Vladimir Davydov wrote:
> On Fri, Jun 08, 2018 at 06:56:36AM +0300, Konstantin Osipov wrote:
> > * Vladimir Davydov <vdavydov.dev@gmail.com> [18/06/04 23:48]:
> > > Since tuples stored in temporary spaces are never written to disk, we
> > > can always delete them immediately, even when a snapshot is in progress.
> > >
> > > Closes #3432
> >
> > OK to push.
>
> Where to? 1.9 or 1.10?
>
> The ticket is on 1.10 milestone, but there's a comment that says it
> should be fixed in 1.9 ...
ping
next prev parent reply other threads:[~2018-06-14 8:23 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-04 11:42 Vladimir Davydov
2018-06-08 3:56 ` Konstantin Osipov
2018-06-08 6:39 ` Vladimir Davydov
2018-06-14 8:23 ` Vladimir Davydov [this message]
2018-06-14 12:57 ` Konstantin Osipov
2018-06-14 13:29 ` Vladimir Davydov
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=20180614082305.padi2xm4czewblwo@esperanza \
--to=vdavydov.dev@gmail.com \
--cc=kostja@tarantool.org \
--cc=tarantool-patches@freelists.org \
--subject='Re: [PATCH] memtx: don'\''t delay deletion of temporary tuples during snapshot' \
/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