What are the options and variables deprecated in MySQL 8.0?

Some of the options and variables that have been deprecated in MySQL 8.0 have been listed below:

• Compression: It tells whether the client connection uses compression in client/server protocol or not. It was deprecated since MySQL 8.0.18.
• expire_logs_days: It purges the binary logs after specific number of days. It was deprecated since MySQL 8.0.3.
• log_syslog: It determines whether to write error log to syslog. It was deprecated since MySQL 8.0.2.
• master-info-file: It helps determine the location and name of file that remembers the source and where the I/O replication thread is, in source's binary log. It was deprecated since MySQL 8.0.18.
• master_info_repository: It determines whether to write connection metadata repository, containing source information and replication I/O thread location in source's binary log, or to the file or the table. It was deprecated since MySQL 8.0.23.
• max_length_for_sort_data: It refers to the maximum number of bytes present in sorted records. It was deprecated since MySQL 8.0.20.
• no-dd-upgrade: It prevents automatic upgrade of data dictionary tables at startup. It was deprecated since MySQL 8.0.16.
• relay_log_info_file: It refers to the file name for applier metadata repository in which the replica records information about the relay logs. It was deprecated since MySQL 8.0.18.
• relay_log_info_repository: It determines whether to write the location of the replication SQL thread in relay logs to the file or to the table. It was deprecated since MySQL 8.0.23.
• slave_compressed_protocol: It is used for the compression of source/replica protocol. It was deprecated since MySQL 8.0.18.
• symbolic-links: It provides permit to the symbolic links for MyISAM tables. It was deprecated since MySQL 8.0.2.

AmitDiwan

Updated on: 24-Feb-2021

251 Views

Kickstart Your Career

Get certified by completing the course

Get Started