[Maria-developers] I_S plugin doubts
Hi i was reading locale_info and qc_info source that i sent in jira changing the last parameter from 0 to SKIP_OPEN_TABLE, change the table from aria engine to memory engine, why? this change something internally in I_S table ? example: from static ST_FIELD_INFO qc_info_fields_queries[]= { {"ENTRY_POSITION_IN_CACHE", MY_INT32_NUM_DECIMAL_DIGITS, MYSQL_TYPE_LONG, 0, 0, 0, 0}, ... to static ST_FIELD_INFO qc_info_fields_queries[]= { {"ENTRY_POSITION_IN_CACHE", MY_INT32_NUM_DECIMAL_DIGITS, MYSQL_TYPE_LONG, 0, 0, 0, SKIP_OPEN_TABLE}, ... -- Roberto Spadim
Second doubt... there's a ENGINE=INFORMATION_SCHEMA that's more 'beautiful' than 'aria' or 'memory', since they aren't this kind of engine like the PERFORMACE_SCHEMA engine
Roberto Spadim <roberto@spadim.com.br> writes:
Second doubt... there's a ENGINE=INFORMATION_SCHEMA that's more 'beautiful' than 'aria' or 'memory', since they aren't this kind of engine like the PERFORMACE_SCHEMA engine
All INFORMATION_SCHEMA tables are first materialised into a MEMORY or MyISAM (or, with MariaDB, possibly Aria) table and then the queries run on them. There is no INFORMATION_SCHEMA storage engine. -- Stewart Smith
maybe just to informe it as information schema? how could i know if a I_S table will be memory or aria or myisam? does mysqld 'parse' it at startup?
Roberto Spadim <roberto@spadim.com.br> writes:
maybe just to informe it as information schema?
how could i know if a I_S table will be memory or aria or myisam? does mysqld 'parse' it at startup?
It depends on the structure of the table and the size it is materialized as. If it's greater than max_heap_table_size it'll be converted to MyISAM/Maria. -- Stewart Smith
hummmm nice =] thanks stewart, well i'm doing it right kkkk the information_schema engine is just to easly view what type the table is but we can see this using the schema thanks!
participants (2)
-
Roberto Spadim -
Stewart Smith