4 Commits (55fbef61fa8d2ced4e7e5d3a773e857c2cf3c3a9)

Author	SHA1	Message	Date
René Cannaò	e983fc6827	Adding support for more MySQL variables ... New variables supported: - lc_messages - lc_time_names - long_query_time - max_execution_time - max_heap_table_size - max_sort_length - optimizer_prune_level - optimizer_search_depth - optimizer_switch - sort_buffer_size - sql_big_selects - timestamp - tmp_table_size Note: sql_big_selects is still not fully supported when combined with max_join_size. In set testing TAP ,set large max_execution_time. If max_execution_time is too small, the TAP test may fails because the queries will timeout.	4 years ago
René Cannaò	2ba9c401f1	Bug fixes in the new implementation of tracking mysql variables ... Better parsing of SET SQL_LOG_BIN . SQL_LOG_BIN is now managed by the same functions that handle boolean variables instead of the now deprecated MySQL_Session::handler_WCD_SS_MCQ_qpo_Parse_SQL_LOG_BIN() For naming convention, enum value SQL_LOG_BIN was renamed to SQL_SQL_LOG_BIN In MySQL_Thread we also deprecated match_regexes[0] , previously used to parse `set sql_log_bin`. Functions Variable::fill_server_internal_session() and Variable::fill_client_internal_session() seems to handle sql_log_bin as a special value. This exception was removed. Fixed a bug in MySQL_Session::generate_proxysql_internal_session_json() where when backend variables needed to be generated, fill_client_internal_session() was incorrectly called instead of fill_server_internal_session() , leading to incorrect values reported by `PROXYSQL INTERNAL SESSION`	4 years ago
René Cannaò	74ab11b84f	Cleanup and fixes on set_testing TAP tests	4 years ago
René Cannaò	d335bfb899	Improvements on how MySQL variables are processed ... Deprecated variables: - net_write_timeout Renamed set_testing-t.csv to set_testing-t.csv.obsolete , and removed net_write_timeout from set_testing-t.csv Variables added to ignore list: - net_write_timeout - net_buffer_length - read_buffer_size - read_rnd_buffer_size Added support for quoting with backtick Renamed `enum variable_name` into `enum mysql_variable_name` for better readibility `enum mysql_variable_name` has variable names alphabetically ordered after SQL_NAME_LAST_LOW_WM `mysql_tracked_variables` has variable names alphabetically ordered after SQL_NAME_LAST_LOW_WM A lot of new variables added in `mysql_tracked_variables` , although not all tracked yet (TODO) In `MySQL_Variables::MySQL_Variables()`: - if `internal_variable_name` in `mysql_tracked_variables` is NULL , it will be automatically initialized - it performs some sanity check between `enum mysql_variable_name` and `mysql_tracked_variables` Testing: - refactored code in set_testing-t.cpp and set_testing-multi-t.cpp - added set_testing-240-t.cpp to test improvements in 2.4.0 - generate_set_session_csv to automatically create set_testing-240.csv used by set_testing-240-t	4 years ago