Previously, ANALYZE routine used to invoke box_space_id_by_nameThank, I've used your explanation.
function, which in turn relies on sysview engine. On the other hand,
ANALYZE processing is surrounded by transaction started in memtx
(_sql_stat1 and _sql_stat4 are system spaces stored in memtx).
Thus, multi-engine transaction error may occur. To avoid such
situation lets use internal schema_find_id() function.
Typo: length.+ * @param len length of @name string.
If nothing is found.
Index AST? I guess “pointer to index otherwise”.
Overall it is sad that we can't use schema_find_id for this purpose.We have already discussed that this is ok. Tnx.
Mb it is worth to refactor this function so that it will take not id but
already encoded key to be found? It is only suggestion tho,
it can be contradictory way..