From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Date: Mon, 23 Jul 2018 22:44:04 +0300 From: Konstantin Osipov Subject: Re: [PATCH] tx: exclude sysview engine from transaction control Message-ID: <20180723194404.GA10149@chai> References: <1e2b7faf141e6b18fdcdf2ea756b28d5d91722fb.1531913079.git.vdavydov.dev@gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1e2b7faf141e6b18fdcdf2ea756b28d5d91722fb.1531913079.git.vdavydov.dev@gmail.com> To: Vladimir Davydov Cc: tarantool-patches@freelists.org List-ID: * Vladimir Davydov [18/07/18 22:16]: > Sysview is a special engine that is used for filtering out objects that > a user can't access due to lack of privileges. Since it's treated as a > separate engine by the transaction manager, we can't query sysview > spaces from a memtx/vinyl transaction. In particular, if called from a > transaction space:format() will return > > error: A multi-statement transaction can not use multiple storage engines > > which is inconvenient. > > To fix this, let's mark sysview engine with a new ENGINE_BYPASS_TX flag > and make the transaction manager skip binding a transaction to an engine > in case this flag is set. > > Closes #3528 Pushed. -- Konstantin Osipov, Moscow, Russia, +7 903 626 22 32 http://tarantool.io - www.twitter.com/kostja_osipov