3 Commits

Author	SHA1	Message	Date
Nirbhay Choubey	3435e8a515	MDEV-7635: Part 1 ... innodb_autoinc_lock_mode = 2 innodb_buffer_pool_dump_at_shutdown = ON innodb_buffer_pool_dump_pct = 25 innodb_buffer_pool_load_at_startup = ON innodb_checksum_algorithm = CRC32 innodb_file_format = Barracuda innodb_large_prefix = ON innodb_log_compressed_pages = ON innodb_purge_threads = 4 innodb_strict_mode = ON binlog_annotate_row_events = ON binlog_format = MIXED binlog-row-event-max-size = 8192 group_concat_max_len = 1M lock_wait_timeout = 86400 log_slow_admin_statements = ON log_slow_slave_statements = ON log_warnings = 2 max_allowed_packet = 16M replicate_annotate_row_events = ON slave_net_timeout = 60 sync_binlog = 1 aria_recover = BACKUP,QUICK myisam_recover_options = BACKUP,QUICK	2017-02-10 06:30:42 -05:00
Oleksandr Byelkin	41106b229e	MDEV-6997: SET STATEMENT last_insert_id FOR ... does not affect the value written to the binlog ... Problem was in reinitialization of first_successful_insert_id_in_prev_stmt_for_binlog after setting variables.	2015-03-13 20:42:30 +01:00
Oleksandr Byelkin	a71e2d23bd	MDEV-7006 MDEV-7007: SET STATEMENT and slow log ... fixed embedded server tests MDEV-7009: SET STATEMENT min_examined_row_limit has no effect MDEV-6948:SET STATEMENT gtid_domain_id = ... FOR has no effect (same for gtid_seq_no and server_id) old values of SET STATENENT variables now saved in its own Query_arena and restored later	2015-03-12 10:19:32 +01:00