You have set innodb_stats_auto_recalc to OFF.
For tables using persistent statistics, what is the outcome of this change?
You have been tasked with creating a QA MySQL instance on a DB host, which already has one large instance in /var/lib/mysql/running as the mysqluser. The MySQL configuration file for the existing instance includes:
The default instance was installed using the OS package manager. The latest binaries for both client and server are already in ENV PATH.
The new instance will run as a different user from the existing instance for security purposes.
You create the new data directory successfully and move on to initialize the new DATADIR.
You verify the output to confirm the operation's success:
[mysqlQA@linux /var/lib/]$ mysqld --initialize --datadir=/var/lib/mysql_QA 2>&1 | tail -n3
2018-05-03T12:16:10.928809Z 0 [ERROR] Could not open file '/var/log/mysqld.log' for error logging:
Permission denied
2018-05-03T12:16:10.928841Z 0 [ERROR] Aborting
[mysqlQA@linux /var/lib/]$
The initialization of the instance has failed.
What would you do to enable the initialization to succeed?
old_alter_table is disabled as shown.
mysql> SELECT @@old_alter_table;
Consider this statement on a RANGE-partitioned table:
mysql> ALTER TABLE orders DROP PARTITION p1, p3;
What is the outcome of executing this statement?
You want to create the first configuration file for a new installation of MySQL.
- You will start mysqldmanually (not automate it to start when the host machine starts or execute as a service).
- You will stop mysqldusing mysqladmin.
- You will interact with mysqldby using only the command-line client mysql.
Which option identifies a maximal set of sections where you can put the "max_allowed_packet=16M" parameter without creating a problem?