From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from localhost (localhost [127.0.0.1]) by turing.freelists.org (Avenir Technologies Mail Multiplex) with ESMTP id 86C22287C0 for ; Wed, 1 Aug 2018 16:25:05 -0400 (EDT) Received: from turing.freelists.org ([127.0.0.1]) by localhost (turing.freelists.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ZOPp0nPtDCYT for ; Wed, 1 Aug 2018 16:25:05 -0400 (EDT) Received: from smtpng3.m.smailru.net (smtpng3.m.smailru.net [94.100.177.149]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by turing.freelists.org (Avenir Technologies Mail Multiplex) with ESMTPS id C160C287BF for ; Wed, 1 Aug 2018 16:25:04 -0400 (EDT) Received: by smtpng3.m.smailru.net with esmtpa (envelope-from ) id 1fkxg6-0008FY-DV for tarantool-patches@freelists.org; Wed, 01 Aug 2018 23:25:02 +0300 Date: Wed, 1 Aug 2018 23:25:01 +0300 From: Konstantin Osipov Subject: [tarantool-patches] Re: [PATCH 24/25] Introduce _vinyl_deferred_delete system space Message-ID: <20180801202501.GD15337@chai> References: <920a0685fd01546464585090dadf57732fa7a696.1532689066.git.vdavydov.dev@gmail.com> <20180731205427.GQ15235@chai> <20180801140018.ti22auajqiwlfyjn@esperanza> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20180801140018.ti22auajqiwlfyjn@esperanza> Sender: tarantool-patches-bounce@freelists.org Errors-to: tarantool-patches-bounce@freelists.org Reply-To: tarantool-patches@freelists.org List-help: List-unsubscribe: List-software: Ecartis version 1.0.0 List-Id: tarantool-patches List-subscribe: List-owner: List-post: List-archive: To: tarantool-patches@freelists.org * Vladimir Davydov [18/08/01 18:14]: > On Tue, Jul 31, 2018 at 11:54:27PM +0300, Konstantin Osipov wrote: > > * Vladimir Davydov [18/07/27 16:55]: > > > The space is a blackhole. It will be used for writing deferred DELETE > > > statements generated by vinyl compaction tasks to WAL so that we can > > > recover deferred DELETEs that hadn't been dumped to disk before the > > > server was restarted. > > > > Why do you actually need a proto space for it? Please feel free to > > put blackhole engine first in the list of engines. > > You mean making this space purely virtual? No record in _space, no info > in snap file, just struct space in the cache? No, I mean no changes in sc_* methods, only a record in _space? > Hmm, I guess we can do that. However, I think that it's kinda weird > to have a space that can be written to, but which doesn't exist in the > data dictionary. This may also result in some anomalies, like the user > can grant access to it although it doesn't actually exist in _space > (yeah, this is pointless, I know, but still). > > Is there any reason to do that? Or do you mean something different by > 'proto space'? -- Konstantin Osipov, Moscow, Russia, +7 903 626 22 32 http://tarantool.io - www.twitter.com/kostja_osipov