[PATCH] tx: exclude sysview engine from transaction control

[Konstantin Osipov]

* Vladimir Davydov <vdavydov.dev at gmail.com> [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