From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Date: Mon, 29 Jul 2019 00:30:49 +0300 From: Konstantin Osipov Subject: Re: [tarantool-patches] Re: [PATCH v5 3/3] box: introduce func_index Message-ID: <20190728213049.GD18418@atlas> References: <25789ea46e8fcec527bd7864209bb6ea2113dca5.1564079799.git.kshcherbatov@tarantool.org> <20190726094958.GA4080@esperanza> <20190726095743.GG9916@atlas> <20190726101032.GB4080@esperanza> <20190726193130.GC14622@atlas> <20190727114248.GB4659@esperanza> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20190727114248.GB4659@esperanza> To: Vladimir Davydov Cc: tarantool-patches@freelists.org, Kirill Shcherbatov , v.shpilevoy@tarantool.org List-ID: * Vladimir Davydov [19/07/28 21:47]: > That's not how things currently work AFAICS. Anyway, this means that > we'll have to have some sort of redundancy: func id should be stored > both in _func_index and _index system spaces. Besides, we'll invoke > different code paths on recovery and during normal operation. I see > clearly now that it's by far better than recovering _func space before > _index space. Thanks for clarification. There are lots of follow up patches related to this work, this is one of them. I hope Kirill will be able to handle all of these follow ups rather than assigned other unrelated work. -- Konstantin Osipov, Moscow, Russia