具体操作请看对应的MySQL版本。
在安装MySQL时，会出现两个文件夹：Data和Install。而配置文件都在Data目录下面，配置文件里有MySQL的所有设置，改错一个就会造成MySQL服务无法启动。
如果安装的时候没有修改安装路径，则默认的Install路径为：C:\Program Files\MySQL\MySQL Server x.y；与之对应的Data路径为：C:\ProgramData\MySQL\MySQL Server x.y。
注意：ProgramData为隐藏文件夹，如何找到自行百度。
问：怎么查看MySQL版本？
答：开始菜单->找到MySQL Installer – Community软件，点击即可查看对应的MySQL Server的版本。
问：如果配置错了，找不到修改的地方导致MySQL服务无法启动怎么办？
答：文章底部提供MySQL的初始配置文件，复制并替换原来的配置文件，重新启动MySQL服务即可。
划重点：替换前请先备份my.ini文件。
本文提供的my.ini文件所安装的路径
MySQL 5.6：
Port=3306
Install：D:\MySQL\Install\MySQL Server 5.6
Data：D:\MySQL\Data\MySQL Server 5.6
MySQL 5.7
Port=3307
Install：D:\MySQL\Install\MySQL Server 5.7
Data：D:\MySQL\Data\MySQL Server 5.7
MySQL 8.0
Port=3308
Install：D:\MySQL\Install\MySQL Server 8.0
Data：D:\MySQL\Data\MySQL Server 8.0
一、错误日志（MySQL自动打开，且无法关闭）
二、查询日志
三、慢查询日志
四、事务日志
五、二进制日志
MySQL5.6
首先在Data目录下面找到my.ini文件，用记事本打开。
找到’# Server Id.’这行，在’server-id=1’下面添加以下内容（路径在Data目录下的data文件夹里）：
html;gutter:true;
log_bin=binlog
log_bin_index=binlog-index</p>
<pre><code>
当然如果你想将Log放在指定文件，也可以这样设置：
;gutter:true;
log_bin=C:/ProgramData/MySQL/MySQL Server 5.6/Log/binlog
log_bin_index=C:/ProgramData/MySQL/MySQL Server 5.6/Log/binlog-index
然后重启MySQL服务即可。
MySQL 5.7
首先在Data目录下面找到my.ini文件，用记事本打开。
找到’# from every other ID in use by any other replication source or replica.’这行，在’server-id=1’下面添加以下内容（路径在Data目录下的data文件夹里）：
html;gutter:true;
log_bin=binlog
log_bin_index=binlog-index</p>
<pre><code>
当然如果你想将Log放在指定文件，也可以这样设置：
;gutter:true;
log_bin=C:/ProgramData/MySQL/MySQL Server 5.7/Log/binlog
log_bin_index=C:/ProgramData/MySQL/MySQL Server 5.7/Log/binlog-index
然后重启MySQL服务即可。
MySQL 8.0
日志默认打开的，在Data目录下的data文件夹里。
当然如果你想将Log放在指定文件，在’# log, which is used for backup and replication.’下面添加：
html;gutter:true;
log_bin=C:/ProgramData/MySQL/MySQL Server 8.0/Log/binlog
log_bin_index=C:/ProgramData/MySQL/MySQL Server 8.0/Log/binlog-index</p>
<pre><code>
然后重启MySQL服务即可。
MySQL 5.6默认my.ini配置：
;gutter:true;
Other default tuning values
MySQL Server Instance Configuration File
———————————————————————-
Generated by the MySQL Server Instance Configuration Wizard
#
#
Installation Instructions
———————————————————————-
#
On Linux you can copy this file to /etc/my.cnf to set global options,
mysql-data-dir/my.cnf to set server-specific options
(@localstatedir@ for this installation) or to
~/.my.cnf to set user-specific options.
#
On Windows, when MySQL has been installed using MySQL Installer you
should keep this file in the ProgramData directory of your server
(e.g. C:\ProgramData\MySQL\MySQL Server X.Y). To make sure the server
reads the config file, use the startup option "–defaults-file".
#
To run the server from the command line, execute this in a
command line shell, e.g.
mysqld –defaults-file="C:\Program Files\MySQL\MySQL Server X.Y\my.ini"
#
To install the server as a Windows service manually, execute this in a
command line shell, e.g.
mysqld –install MySQLXY –defaults-file="C:\Program Files\MySQL\MySQL Server X.Y\my.ini"
#
And then execute this in a command line shell to start the server, e.g.
net start MySQLXY
#
#
Guidelines for editing this file
———————————————————————-
#
In this file, you can use all long options that the program supports.
If you want to know the options a program supports, start the program
with the "–help" option.
#
More detailed information about the individual options can also be
found in the manual.
#
For advice on how to change settings please see
https://dev.mysql.com/doc/refman/5.6/en/server-configuration-defaults.html
#
#
CLIENT SECTION
———————————————————————-
#
The following options will be read by MySQL client applications.
Note that only client applications shipped by MySQL are guaranteed
to read this section. If you want your own MySQL client program to
honor these values, you need to specify it as an option during the
MySQL client library initialization.
#
[client]
pipe=
socket=MYSQL
port=3306
[mysql]
no-beep
default-character-set=
SERVER SECTION
———————————————————————-
#
The following options will be read by the MySQL Server. Make sure that
you have installed the server correctly (see above) so it reads this
file.
#
server_type=3
[mysqld]
The next three options are mutually exclusive to SERVER_PORT below.
skip-networking
enable-named-pipe
shared-memory
shared-memory-base-name=MYSQL
The Pipe the MySQL Server will use
socket=MYSQL
The access control granted to clients on the named pipe created by the MySQL Server.
named-pipe-full-access-group=
The TCP/IP Port the MySQL Server will listen on
port=3306
Path to installation directory. All paths are usually resolved relative to this.
basedir="D:/MySQL/Install/MySQL Server 5.6/"
Path to the database root
datadir=D:/MySQL/Data/MySQL Server 5.6/Data
The default character set that will be used when a new schema or table is
created and no character set is defined
character-set-server=
The default storage engine that will be used when create new tables when
default-storage-engine=INNODB
Set the SQL mode to strict
sql-mode="STRICT_TRANS_TABLES,NO_AUTO_CREATE_USER,NO_ENGINE_SUBSTITUTION"
General and Slow logging.
log-output=FILE
general-log=0
general_log_file="ALONE.log"
slow-query-log=1
slow_query_log_file="ALONE-slow.log"
long_query_time=10
Binary Logging.
log-bin
Error Logging.
log-error="ALONE.err"
Server Id.
server-id=1
Indicates how table and database names are stored on disk and used in MySQL.
Value = 0: Table and database names are stored on disk using the lettercase specified in the
CREATE TABLE or CREATE DATABASE statement. Name comparisons are case sensitive.
You should not set this variable to 0 if you are running MySQL on a system that has
case-insensitive file names (such as Windows or macOS).
Value = 1: Table names are stored in lowercase on disk and name comparisons are not
case-sensitive. MySQL converts all table names to lowercase on storage and lookup.
This behavior also applies to database names and table aliases.
Value = 3, Table and database names are stored on disk using the lettercase specified in the
CREATE TABLE or CREATE DATABASE statement, but MySQL converts them to lowercase on
lookup. Name comparisons are not case sensitive. This works only on file systems
that are not case-sensitive! InnoDB table names and view names are stored in
lowercase, as for Value = 1.
NOTE: lower_case_table_names can only be configured when initializing the server.
Changing the lower_case_table_names setting after the server is initialized is prohibited.
lower_case_table_names=1
Secure File Priv.
secure-file-priv="D:/MySQL/Data/MySQL Server 5.6/Uploads"
The maximum amount of concurrent sessions the MySQL server will
allow. One of these connections will be reserved for a user with
SUPER privileges to allow the administrator to login even if the
connection limit has been reached.
max_connections=151
Query cache is used to cache SELECT results and later return them
without actual executing the same query once again. Having the query
cache enabled may result in significant speed improvements, if your
have a lot of identical queries and rarely changing tables. See the
"Qcache_lowmem_prunes" status variable to check if the current value
is high enough for your load.
Note: In case your tables change very often or if your queries are
textually different every time, the query cache may result in a
slowdown instead of a performance improvement.
query_cache_size=1M
The number of open tables for all threads. Increasing this value
increases the number of file descriptors that mysqld requires.
Therefore you have to make sure to set the amount of open files
allowed to at least 4096 in the variable "open-files-limit" in
section [mysqld_safe]
table_open_cache=
Maximum size for internal (in-memory) temporary tables. If a table
grows larger than this value, it is automatically converted to disk
based table This limitation is for a single table. There can be many
of them.
tmp_table_size=8M
How many threads we should keep in a cache for reuse. When a client
disconnects, the client’s threads are put in the cache if there aren’t
more than thread_cache_size threads from before. This greatly reduces
the amount of thread creations needed if you have a lot of new
connections. (Normally this doesn’t give a notable performance
improvement if you have a good thread implementation.)
thread_cache_size=10
#*** MyISAM Specific options
The maximum size of the temporary file MySQL is allowed to use while
recreating the index (during REPAIR, ALTER TABLE or LOAD DATA INFILE.
If the file-size would be bigger than this, the index will be created
through the key cache (which is slower).
myisam_max_sort_file_size=100G
The size of the buffer that is allocated when sorting MyISAM indexes
during a REPAIR TABLE or when creating indexes with CREATE INDEX
or ALTER TABLE.
myisam_sort_buffer_size=8M
Size of the Key Buffer, used to cache index blocks for MyISAM tables.
Do not set it larger than 30% of your available memory, as some memory
is also required by the OS to cache rows. Even if you’re not using
MyISAM tables, you should still set it to 8-64M as it will also be
used for internal temporary disk tables.
key_buffer_size=8M
Size of the buffer used for doing full table scans of MyISAM tables.
Allocated per thread, if a full scan is needed.
read_buffer_size=15K
read_rnd_buffer_size=256K
#*** INNODB Specific options ***
innodb_data_home_dir=
Use this option if you have a MySQL server with InnoDB support enabled
but you do not plan to use it. This will save memory and disk space
and speed up some things.
skip-innodb
Additional memory pool that is used by InnoDB to store metadata
information. If InnoDB requires more memory for this purpose it will
start to allocate it from the OS. As this is fast enough on most
recent operating systems, you normally do not need to change this
value. SHOW INNODB STATUS will display the current amount used.
innodb_additional_mem_pool_size=2M
If set to 1, InnoDB will flush (fsync) the transaction logs to the
disk at each commit, which offers full ACID behavior. If you are
willing to compromise this safety, and you are running small
transactions, you may set this to 0 or 2 to reduce disk I/O to the
logs. Value 0 means that the log is only written to the log file and
the log file flushed to disk approximately once per second. Value 2
means the log is written to the log file at each commit, but the log
file is only flushed to disk approximately once per second.
innodb_flush_log_at_trx_commit=1
The size in bytes of the buffer that InnoDB uses to write to the log files
on disk. The default is 8MB. A large log buffer enables large transactions to
run without the need to write the log to disk before the transactions commit.
Thus, if you have transactions that update, insert, or delete many rows,
making the log buffer larger saves disk I/O.
innodb_log_buffer_size=8M
The size in bytes of the buffer pool, the memory area where InnoDB caches table
and index data. The default value is 134217728 bytes (128MB). The maximum value
depends on the CPU architecture; the maximum is 4294967295 (232-1) on 32-bit
systems and 18446744073709551615 (264-1) on 64-bit systems. On 32-bit systems,
the CPU architecture and operating system may impose a lower practical maximum
size than the stated maximum. When the size of the buffer pool is greater than
1GB, setting innodb_buffer_pool_instances to a value greater than 1 can improve
the scalability on a busy server.
innodb_buffer_pool_size=128M
Size of each log file in a log group. You should set the combined size
of log files to about 25%-100% of your buffer pool size to avoid
unneeded buffer pool flush activity on log file overwrite. However,
note that a larger logfile size will increase the time needed for the
recovery process.
innodb_log_file_size=48M
Number of threads allowed inside the InnoDB kernel. The optimal value
depends highly on the application, hardware as well as the OS
scheduler properties. A too high value may lead to thread thrashing.
innodb_thread_concurrency=8
The increment size (in MB) for extending the size of an auto-extend InnoDB system tablespace file when it becomes full.
innodb_autoextend_increment=64
The number of regions that the InnoDB buffer pool is divided into.
For systems with buffer pools in the multi-gigabyte range, dividing the buffer pool into separate instances can improve concurrency,
by reducing contention as different threads read and write to cached pages.
innodb_buffer_pool_instances=8
Determines the number of threads that can enter InnoDB concurrently.
innodb_concurrency_tickets=5000
Specifies how long in milliseconds (ms) a block inserted into the old sublist must stay there after its first access before
it can be moved to the new sublist.
innodb_old_blocks_time=1000
When this variable is enabled, InnoDB updates statistics during metadata statements.
innodb_stats_on_metadata=0
When innodb_file_per_table is enabled (the default in 5.6.6 and higher), InnoDB stores the data and indexes for each newly created table
in a separate .ibd file, rather than in the system tablespace.
innodb_file_per_table=1
Use the following list of values: 0 for crc32, 1 for strict_crc32, 2 for innodb, 3 for strict_innodb, 4 for none, 5 for strict_none.
innodb_checksum_algorithm=0
The number of outstanding connection requests MySQL can have.
This option is useful when the main MySQL thread gets many connection requests in a very short time.
It then takes some time (although very little) for the main thread to check the connection and start a new thread.
The back_log value indicates how many requests can be stacked during this short time before MySQL momentarily
stops answering new requests.
You need to increase this only if you expect a large number of connections in a short period of time.
back_log=80
If this is set to a nonzero value, all tables are closed every flush_time seconds to free up resources and
synchronize unflushed data to disk.
This option is best used only on systems with minimal resources.
flush_time=0
The minimum size of the buffer that is used for plain index scans, range index scans, and joins that do not use
indexes and thus perform full table scans.
join_buffer_size=256K
The maximum size of one packet or any generated or intermediate string, or any parameter sent by the
mysql_stmt_send_long_data() C API function.
max_allowed_packet=4M
If more than this many successive connection requests from a host are interrupted without a successful connection,
the server blocks that host from performing further connections.
max_connect_errors=100
Changes the number of file descriptors available to mysqld.
You should try increasing the value of this option if mysqld gives you the error "Too many open files".
open_files_limit=161
Set the query cache type. 0 for OFF, 1 for ON and 2 for DEMAND.
query_cache_type=1
If you see many sort_merge_passes per second in SHOW GLOBAL STATUS output, you can consider increasing the
sort_buffer_size value to speed up ORDER BY or GROUP BY operations that cannot be improved with query optimization
or improved indexing.
sort_buffer_size=256K
The number of table definitions (from .frm files) that can be stored in the definition cache.
If you use a large number of tables, you can create a large table definition cache to speed up opening of tables.
The table definition cache takes less space and does not use file descriptors, unlike the normal table cache.
The minimum and default values are both 400.
table_definition_cache=400
Specify the maximum size of a row-based binary log event, in bytes.
Rows are grouped into events smaller than this size if possible. The value should be a multiple of 256.
binlog_row_event_max_size=8K
If the value of this variable is greater than 0, a replica synchronizes its master.info file to disk.
(using fdatasync()) after every sync_master_info events.
sync_master_info=10000
If the value of this variable is greater than 0, the MySQL server synchronizes its relay log to disk.
(using fdatasync()) after every sync_relay_log writes to the relay log.
sync_relay_log=10000
If the value of this variable is greater than 0, a replica synchronizes its relay-log.info file to disk.
(using fdatasync()) after every sync_relay_log_info transactions.
sync_relay_log_info=10000
Load mysql plugins at start."plugin_x ; plugin_y".
plugin_load
MySQL 5.7默认my.ini配置：
html;gutter:true;
Other default tuning values
MySQL Server Instance Configuration File</p>
<hr />
<p>Generated by the MySQL Server Instance Configuration Wizard</p>
<h1></h1>
<h1></h1>
<h2>Installation Instructions</h2>
<h1></h1>
<p>On Linux you can copy this file to /etc/my.cnf to set global options,
mysql-data-dir/my.cnf to set server-specific options
(@localstatedir@ for this installation) or to
~/.my.cnf to set user-specific options.</p>
<h1></h1>
<p>On Windows, when MySQL has been installed using MySQL Installer you
should keep this file in the ProgramData directory of your server
(e.g. C:\ProgramData\MySQL\MySQL Server X.Y). To make sure the server
reads the config file, use the startup option "--defaults-file".</p>
<h1></h1>
<p>To run the server from the command line, execute this in a
command line shell, e.g.</p>
<p>mysqld --defaults-file="C:\Program Files\MySQL\MySQL Server X.Y\my.ini"</p>
<h1></h1>
<p>To install the server as a Windows service manually, execute this in a
command line shell, e.g.</p>
<p>mysqld --install MySQLXY --defaults-file="C:\Program Files\MySQL\MySQL Server X.Y\my.ini"</p>
<h1></h1>
<p>And then execute this in a command line shell to start the server, e.g.</p>
<p>net start MySQLXY</p>
<h1></h1>
<h1></h1>
<h2>Guidelines for editing this file</h2>
<h1></h1>
<p>In this file, you can use all long options that the program supports.</p>
<p>If you want to know the options a program supports, start the program
with the "--help" option.</p>
<h1></h1>
<p>More detailed information about the individual options can also be
found in the manual.</p>
<h1></h1>
<p>For advice on how to change settings please see
https://dev.mysql.com/doc/refman/5.7/en/server-configuration-defaults.html</p>
<h1></h1>
<h1></h1>
<h2>CLIENT SECTION</h2>
<h1></h1>
<p>The following options will be read by MySQL client applications.</p>
<p>Note that only client applications shipped by MySQL are guaranteed
to read this section. If you want your own MySQL client program to
honor these values, you need to specify it as an option during the
MySQL client library initialization.</p>
<h1></h1>
<p>[client]</p>
<p>pipe=</p>
<p>socket=MYSQL</p>
<p>port=3307</p>
<p>[mysql]
no-beep</p>
<p>default-character-set=</p>
<h2>SERVER SECTION</h2>
<h1></h1>
<p>The following options will be read by the MySQL Server. Make sure that
you have installed the server correctly (see above) so it reads this
file.</p>
<h1></h1>
<p>server_type=3
[mysqld]</p>
<p>The next three options are mutually exclusive to SERVER_PORT below.</p>
<p>skip-networking
enable-named-pipe
shared-memory</p>
<p>shared-memory-base-name=MYSQL</p>
<p>The Pipe the MySQL Server will use
socket=MYSQL</p>
<p>The access control granted to clients on the named pipe created by the MySQL Server.</p>
<p>named-pipe-full-access-group=</p>
<p>The TCP/IP Port the MySQL Server will listen on
port=3307</p>
<p>Path to installation directory. All paths are usually resolved relative to this.</p>
<p>basedir="D:/MySQL/Install/MySQL Server 5.7/"</p>
<p>Path to the database root
datadir=D:/MySQL/Data/MySQL Server 5.7/Data</p>
<p>The default character set that will be used when a new schema or table is
created and no character set is defined
character-set-server=</p>
<p>The default storage engine that will be used when create new tables when
default-storage-engine=INNODB</p>
<p>Set the SQL mode to strict
sql-mode="STRICT_TRANS_TABLES,NO_AUTO_CREATE_USER,NO_ENGINE_SUBSTITUTION"</p>
<p>General and Slow logging.</p>
<p>log-output=FILE</p>
<p>general-log=0</p>
<p>general_log_file="ALONE.log"</p>
<p>slow-query-log=1</p>
<p>slow_query_log_file="ALONE-slow.log"</p>
<p>long_query_time=10</p>
<p>Error Logging.</p>
<p>log-error="ALONE.err"</p>
<p><strong><em>*</em> Group Replication Related </strong>***
Specifies the base name to use for binary log files. With binary logging
enabled, the server logs all statements that change data to the binary
log, which is used for backup and replication.</p>
<p>log-bin</p>
<p><strong><em>*</em> Group Replication Related </strong>***
Specifies the server ID. For servers that are used in a replication topology,
you must specify a unique server ID for each replication server, in the
range from 1 to 2^32 − 1. "Unique" means that each ID must be different
from every other ID in use by any other replication source or replica.</p>
<p>server-id=1</p>
<p><strong><em>*</em> Group Replication Related </strong>***
Defines the algorithm used to hash the writes extracted during a transaction. If you
are using Group Replication, this variable must be set to XXHASH64 because the process
of extracting the writes from a transaction is required for conflict detection on all
group members.</p>
<p>transaction_write_set_extraction=0.0
lower_case_table_names=1</p>
<p>Secure File Priv.</p>
<p>secure-file-priv="D:/MySQL/Data/MySQL Server 5.7/Uploads"</p>
<p>The maximum amount of concurrent sessions the MySQL server will
allow. One of these connections will be reserved for a user with
SUPER privileges to allow the administrator to login even if the
connection limit has been reached.</p>
<p>max_connections=151</p>
<p>The number of open tables for all threads. Increasing this value
increases the number of file descriptors that mysqld requires.</p>
<p>Therefore you have to make sure to set the amount of open files
allowed to at least 4096 in the variable "open-files-limit" in
section [mysqld_safe]
table_open_cache=2000</p>
<p>Maximum size for internal (in-memory) temporary tables. If a table
grows larger than this value, it is automatically converted to disk
based table This limitation is for a single table. There can be many
of them.</p>
<p>tmp_table_size=8M</p>
<p>How many threads we should keep in a cache for reuse. When a client
disconnects, the client's threads are put in the cache if there aren't
more than thread_cache_size threads from before. This greatly reduces
the amount of thread creations needed if you have a lot of new
connections. (Normally this doesn't give a notable performance
improvement if you have a good thread implementation.)
thread_cache_size=10</p>
<h1>*** MyISAM Specific options</h1>
<p>The maximum size of the temporary file MySQL is allowed to use while
recreating the index (during REPAIR, ALTER TABLE or LOAD DATA INFILE.</p>
<p>If the file-size would be bigger than this, the index will be created
through the key cache (which is slower).</p>
<p>myisam_max_sort_file_size=100G</p>
<p>The size of the buffer that is allocated when sorting MyISAM indexes
during a REPAIR TABLE or when creating indexes with CREATE INDEX
or ALTER TABLE.</p>
<p>myisam_sort_buffer_size=8M</p>
<p>Size of the Key Buffer, used to cache index blocks for MyISAM tables.</p>
<p>Do not set it larger than 30% of your available memory, as some memory
is also required by the OS to cache rows. Even if you're not using
MyISAM tables, you should still set it to 8-64M as it will also be
used for internal temporary disk tables.</p>
<p>key_buffer_size=8M</p>
<p>Size of the buffer used for doing full table scans of MyISAM tables.</p>
<p>Allocated per thread, if a full scan is needed.</p>
<p>read_buffer_size=14K</p>
<p>read_rnd_buffer_size=256K</p>
<h1><strong><em> INNODB Specific options </em></strong></h1>
<p>innodb_data_home_dir=</p>
<p>Use this option if you have a MySQL server with InnoDB support enabled
but you do not plan to use it. This will save memory and disk space
and speed up some things.</p>
<p>skip-innodb</p>
<p>If set to 1, InnoDB will flush (fsync) the transaction logs to the
disk at each commit, which offers full ACID behavior. If you are
willing to compromise this safety, and you are running small
transactions, you may set this to 0 or 2 to reduce disk I/O to the
logs. Value 0 means that the log is only written to the log file and
the log file flushed to disk approximately once per second. Value 2
means the log is written to the log file at each commit, but the log
file is only flushed to disk approximately once per second.</p>
<p>innodb_flush_log_at_trx_commit=1</p>
<p>The size of the buffer InnoDB uses for buffering log data. As soon as
it is full, InnoDB will have to flush it to disk. As it is flushed
once per second anyway, it does not make sense to have it very large
(even with long transactions).</p>
<p>innodb_log_buffer_size=16M</p>
<p>The size in bytes of the buffer pool, the memory area where InnoDB caches table
and index data. The default value is 134217728 bytes (128MB). The maximum value
depends on the CPU architecture; the maximum is 4294967295 (232-1) on 32-bit
systems and 18446744073709551615 (264-1) on 64-bit systems. On 32-bit systems,
the CPU architecture and operating system may impose a lower practical maximum
size than the stated maximum. When the size of the buffer pool is greater than
1GB, setting innodb_buffer_pool_instances to a value greater than 1 can improve
the scalability on a busy server.</p>
<p>innodb_buffer_pool_size=128M</p>
<p>Size of each log file in a log group. You should set the combined size
of log files to about 25%-100% of your buffer pool size to avoid
unneeded buffer pool flush activity on log file overwrite. However,
note that a larger logfile size will increase the time needed for the
recovery process.</p>
<p>innodb_log_file_size=48M</p>
<p>Number of threads allowed inside the InnoDB kernel. The optimal value
depends highly on the application, hardware as well as the OS
scheduler properties. A too high value may lead to thread thrashing.</p>
<p>innodb_thread_concurrency=8</p>
<p>The increment size (in MB) for extending the size of an auto-extend InnoDB system tablespace file when it becomes full.</p>
<p>innodb_autoextend_increment=64</p>
<p>The number of regions that the InnoDB buffer pool is divided into.</p>
<p>For systems with buffer pools in the multi-gigabyte range, dividing the buffer pool into separate instances can improve concurrency,
by reducing contention as different threads read and write to cached pages.</p>
<p>innodb_buffer_pool_instances=8</p>
<p>Determines the number of threads that can enter InnoDB concurrently.</p>
<p>innodb_concurrency_tickets=5000</p>
<p>Specifies how long in milliseconds (ms) a block inserted into the old sublist must stay there after its first access before
it can be moved to the new sublist.</p>
<p>innodb_old_blocks_time=1000</p>
<p>When this variable is enabled, InnoDB updates statistics during metadata statements.</p>
<p>innodb_stats_on_metadata=0</p>
<p>When innodb_file_per_table is enabled (the default in 5.6.6 and higher), InnoDB stores the data and indexes for each newly created table
in a separate .ibd file, rather than in the system tablespace.</p>
<p>innodb_file_per_table=1</p>
<p>Use the following list of values: 0 for crc32, 1 for strict_crc32, 2 for innodb, 3 for strict_innodb, 4 for none, 5 for strict_none.</p>
<p>innodb_checksum_algorithm=0</p>
<p>The number of outstanding connection requests MySQL can have.</p>
<p>This option is useful when the main MySQL thread gets many connection requests in a very short time.</p>
<p>It then takes some time (although very little) for the main thread to check the connection and start a new thread.</p>
<p>The back_log value indicates how many requests can be stacked during this short time before MySQL momentarily
stops answering new requests.</p>
<p>You need to increase this only if you expect a large number of connections in a short period of time.</p>
<p>back_log=80</p>
<p>If this is set to a nonzero value, all tables are closed every flush_time seconds to free up resources and
synchronize unflushed data to disk.</p>
<p>This option is best used only on systems with minimal resources.</p>
<p>flush_time=0</p>
<p>The minimum size of the buffer that is used for plain index scans, range index scans, and joins that do not use
indexes and thus perform full table scans.</p>
<p>join_buffer_size=256K</p>
<p>The maximum size of one packet or any generated or intermediate string, or any parameter sent by the
mysql_stmt_send_long_data() C API function.</p>
<p>max_allowed_packet=4M</p>
<p>If more than this many successive connection requests from a host are interrupted without a successful connection,
the server blocks that host from performing further connections.</p>
<p>max_connect_errors=100</p>
<p>Changes the number of file descriptors available to mysqld.</p>
<p>You should try increasing the value of this option if mysqld gives you the error "Too many open files".</p>
<p>open_files_limit=4161</p>
<p>If you see many sort_merge_passes per second in SHOW GLOBAL STATUS output, you can consider increasing the
sort_buffer_size value to speed up ORDER BY or GROUP BY operations that cannot be improved with query optimization
or improved indexing.</p>
<p>sort_buffer_size=256K</p>
<p>The number of table definitions (from .frm files) that can be stored in the definition cache.</p>
<p>If you use a large number of tables, you can create a large table definition cache to speed up opening of tables.</p>
<p>The table definition cache takes less space and does not use file descriptors, unlike the normal table cache.</p>
<p>The minimum and default values are both 400.</p>
<p>table_definition_cache=1400</p>
<p>Specify the maximum size of a row-based binary log event, in bytes.</p>
<p>Rows are grouped into events smaller than this size if possible. The value should be a multiple of 256.</p>
<p>binlog_row_event_max_size=8K</p>
<p>If the value of this variable is greater than 0, a replica synchronizes its master.info file to disk.</p>
<p>(using fdatasync()) after every sync_master_info events.</p>
<p>sync_master_info=10000</p>
<p>If the value of this variable is greater than 0, the MySQL server synchronizes its relay log to disk.</p>
<p>(using fdatasync()) after every sync_relay_log writes to the relay log.</p>
<p>sync_relay_log=10000</p>
<p>If the value of this variable is greater than 0, a replica synchronizes its relay-log.info file to disk.</p>
<p>(using fdatasync()) after every sync_relay_log_info transactions.</p>
<p>sync_relay_log_info=10000</p>
<p>Load mysql plugins at start."plugin_x ; plugin_y".</p>
<p>plugin_load</p>
<p>The TCP/IP Port the MySQL Server X Protocol will listen on.</p>
<p>loose_mysqlx_port=33060</p>
<pre><code>
MySQL 8.0默认my.ini配置：
;gutter:true;
Other default tuning values
MySQL Server Instance Configuration File
———————————————————————-
Generated by the MySQL Server Instance Configuration Wizard
#
#
Installation Instructions
———————————————————————-
#
On Linux you can copy this file to /etc/my.cnf to set global options,
mysql-data-dir/my.cnf to set server-specific options
(@localstatedir@ for this installation) or to
~/.my.cnf to set user-specific options.
#
On Windows, when MySQL has been installed using MySQL Installer you
should keep this file in the ProgramData directory of your server
(e.g. C:\ProgramData\MySQL\MySQL Server X.Y). To make sure the server
reads the config file, use the startup option "–defaults-file".
#
To run the server from the command line, execute this in a
command line shell, e.g.
mysqld –defaults-file="C:\Program Files\MySQL\MySQL Server X.Y\my.ini"
#
To install the server as a Windows service manually, execute this in a
command line shell, e.g.
mysqld –install MySQLXY –defaults-file="C:\Program Files\MySQL\MySQL Server X.Y\my.ini"
#
And then execute this in a command line shell to start the server, e.g.
net start MySQLXY
#
#
Guidelines for editing this file
———————————————————————-
#
In this file, you can use all long options that the program supports.
If you want to know the options a program supports, start the program
with the "–help" option.
#
More detailed information about the individual options can also be
found in the manual.
#
For advice on how to change settings please see
https://dev.mysql.com/doc/refman/8.0/en/server-configuration-defaults.html
#
#
CLIENT SECTION
———————————————————————-
#
The following options will be read by MySQL client applications.
Note that only client applications shipped by MySQL are guaranteed
to read this section. If you want your own MySQL client program to
honor these values, you need to specify it as an option during the
MySQL client library initialization.
#
[client]
pipe=
socket=MYSQL
port=3308
[mysql]
no-beep
default-character-set=
SERVER SECTION
———————————————————————-
#
The following options will be read by the MySQL Server. Make sure that
you have installed the server correctly (see above) so it reads this
file.
#
server_type=3
[mysqld]
The next three options are mutually exclusive to SERVER_PORT below.
skip-networking
enable-named-pipe
shared-memory
shared-memory-base-name=MYSQL
The Pipe the MySQL Server will use.
socket=MYSQL
The access control granted to clients on the named pipe created by the MySQL Server.
named-pipe-full-access-group=
The TCP/IP Port the MySQL Server will listen on
port=3308
Path to installation directory. All paths are usually resolved relative to this.
basedir="D:/MySQL/Install/MySQL Server 8.0/"
Path to the database root
datadir=D:/MySQL/Data/MySQL Server 8.0\Data
The default character set that will be used when a new schema or table is
created and no character set is defined
character-set-server=
Administers multifactor authentication (MFA) capabilities. It applies to the authentication
factor-related clauses of CREATE USER and ALTER USER statements used to manage MySQL account
definitions, where "factor" corresponds to an authentication method or plugin associated
with an account.
authentication_policy=caching_sha2_password,,
The default storage engine that will be used when create new tables when
default-storage-engine=INNODB
Set the SQL mode to strict
sql-mode="STRICT_TRANS_TABLES,NO_ENGINE_SUBSTITUTION"
General and Slow logging.
log-output=FILE
general-log=0
general_log_file="ALONE.log"
slow-query-log=1
slow_query_log_file="ALONE-slow.log"
long_query_time=10
Error Logging.
log-error="ALONE.err"
***** Group Replication Related *****
Specifies the base name to use for binary log files. With binary logging
enabled, the server logs all statements that change data to the binary
log, which is used for backup and replication.
log-bin="ALONE-bin"
***** Group Replication Related *****
Specifies the server ID. For servers that are used in a replication topology,
you must specify a unique server ID for each replication server, in the
range from 1 to 2^32 − 1. "Unique" means that each ID must be different
from every other ID in use by any other source or replica.
server-id=1
NOTE: Modify this value after Server initialization won’t take effect.
lower_case_table_names=1
Secure File Priv.
secure-file-priv="D:/MySQL/Data/MySQL Server 8.0/Uploads"
The maximum amount of concurrent sessions the MySQL server will
allow. One of these connections will be reserved for a user with
SUPER privileges to allow the administrator to login even if the
connection limit has been reached.
max_connections=151
The number of open tables for all threads. Increasing this value
increases the number of file descriptors that mysqld requires.
Therefore you have to make sure to set the amount of open files
allowed to at least 4096 in the variable "open-files-limit" in
section [mysqld_safe]
table_open_cache=4000
Maximum size for internal (in-memory) temporary tables. If a table
grows larger than this value, it is automatically converted to disk
based table This limitation is for a single table. There can be many
of them.
tmp_table_size=8M
How many threads we should keep in a cache for reuse. When a client
disconnects, the client’s threads are put in the cache if there aren’t
more than thread_cache_size threads from before. This greatly reduces
the amount of thread creations needed if you have a lot of new
connections. (Normally this doesn’t give a notable performance
improvement if you have a good thread implementation.)
thread_cache_size=10
#*** MyISAM Specific options
The maximum size of the temporary file MySQL is allowed to use while
recreating the index (during REPAIR, ALTER TABLE or LOAD DATA INFILE.
If the file-size would be bigger than this, the index will be created
through the key cache (which is slower).
myisam_max_sort_file_size=100G
The size of the buffer that is allocated when sorting MyISAM indexes
during a REPAIR TABLE or when creating indexes with CREATE INDEX
or ALTER TABLE.
myisam_sort_buffer_size=8M
Size of the Key Buffer, used to cache index blocks for MyISAM tables.
Do not set it larger than 30% of your available memory, as some memory
is also required by the OS to cache rows. Even if you’re not using
MyISAM tables, you should still set it to 8-64M as it will also be
used for internal temporary disk tables.
key_buffer_size=8M
Size of the buffer used for doing full table scans of MyISAM tables.
Allocated per thread, if a full scan is needed.
read_buffer_size=15K
read_rnd_buffer_size=256K
#*** INNODB Specific options ***
innodb_data_home_dir=
Use this option if you have a MySQL server with InnoDB support enabled
but you do not plan to use it. This will save memory and disk space
and speed up some things.
skip-innodb
If set to 1, InnoDB will flush (fsync) the transaction logs to the
disk at each commit, which offers full ACID behavior. If you are
willing to compromise this safety, and you are running small
transactions, you may set this to 0 or 2 to reduce disk I/O to the
logs. Value 0 means that the log is only written to the log file and
the log file flushed to disk approximately once per second. Value 2
means the log is written to the log file at each commit, but the log
file is only flushed to disk approximately once per second.
innodb_flush_log_at_trx_commit=1
The size in bytes of the buffer that InnoDB uses to write to the log files
on disk. The default is 16MB. A large log buffer enables large transactions to
run without the need to write the log to disk before the transactions commit.
Thus, if you have transactions that update, insert, or delete many rows,
making the log buffer larger saves disk I/O.
innodb_log_buffer_size=16M
The size in bytes of the buffer pool, the memory area where InnoDB caches table
and index data. The default value is 134217728 bytes (128MB). The maximum value
depends on the CPU architecture; the maximum is 4294967295 (232-1) on 32-bit
systems and 18446744073709551615 (264-1) on 64-bit systems. On 32-bit systems,
the CPU architecture and operating system may impose a lower practical maximum
size than the stated maximum. When the size of the buffer pool is greater than
1GB, setting innodb_buffer_pool_instances to a value greater than 1 can improve
the scalability on a busy server.
innodb_buffer_pool_size=128M
Size of each log file in a log group. You should set the combined size
of log files to about 25%-100% of your buffer pool size to avoid
unneeded buffer pool flush activity on log file overwrite. However,
note that a larger logfile size will increase the time needed for the
recovery process.
innodb_log_file_size=48M
Number of threads allowed inside the InnoDB kernel. The optimal value
depends highly on the application, hardware as well as the OS
scheduler properties. A too high value may lead to thread thrashing.
innodb_thread_concurrency=8
The increment size (in MB) for extending the size of an auto-extend InnoDB system tablespace file when it becomes full.
innodb_autoextend_increment=64
The number of regions that the InnoDB buffer pool is divided into.
For systems with buffer pools in the multi-gigabyte range, dividing the buffer pool into separate instances can improve concurrency,
by reducing contention as different threads read and write to cached pages.
innodb_buffer_pool_instances=8
Determines the number of threads that can enter InnoDB concurrently.
innodb_concurrency_tickets=5000
Specifies how long in milliseconds (ms) a block inserted into the old sublist must stay there after its first access before
it can be moved to the new sublist.
innodb_old_blocks_time=1000
When this variable is enabled, InnoDB updates statistics during metadata statements.
innodb_stats_on_metadata=0
When innodb_file_per_table is enabled (the default in 5.6.6 and higher), InnoDB stores the data and indexes for each newly created table
in a separate .ibd file, rather than in the system tablespace.
innodb_file_per_table=1
Use the following list of values: 0 for crc32, 1 for strict_crc32, 2 for innodb, 3 for strict_innodb, 4 for none, 5 for strict_none.
innodb_checksum_algorithm=0
The number of outstanding connection requests MySQL can have.
This option is useful when the main MySQL thread gets many connection requests in a very short time.
It then takes some time (although very little) for the main thread to check the connection and start a new thread.
The back_log value indicates how many requests can be stacked during this short time before MySQL momentarily
stops answering new requests.
You need to increase this only if you expect a large number of connections in a short period of time.
back_log=80
If this is set to a nonzero value, all tables are closed every flush_time seconds to free up resources and
synchronize unflushed data to disk.
This option is best used only on systems with minimal resources.
flush_time=0
The minimum size of the buffer that is used for plain index scans, range index scans, and joins that do not use
indexes and thus perform full table scans.
join_buffer_size=256K
The maximum size of one packet or any generated or intermediate string, or any parameter sent by the
mysql_stmt_send_long_data() C API function.
max_allowed_packet=64M
If more than this many successive connection requests from a host are interrupted without a successful connection,
the server blocks that host from performing further connections.
max_connect_errors=100
Changes the number of file descriptors available to mysqld.
You should try increasing the value of this option if mysqld gives you the error "Too many open files".
open_files_limit=8161
If you see many sort_merge_passes per second in SHOW GLOBAL STATUS output, you can consider increasing the
sort_buffer_size value to speed up ORDER BY or GROUP BY operations that cannot be improved with query optimization
or improved indexing.
sort_buffer_size=256K
The number of table definitions (from .frm files) that can be stored in the definition cache.
If you use a large number of tables, you can create a large table definition cache to speed up opening of tables.
The table definition cache takes less space and does not use file descriptors, unlike the normal table cache.
The minimum and default values are both 400.
table_definition_cache=2000
Specify the maximum size of a row-based binary log event, in bytes.
Rows are grouped into events smaller than this size if possible. The value should be a multiple of 256.
binlog_row_event_max_size=8K
If the value of this variable is greater than 0, a replica synchronizes its master.info file to disk.
(using fdatasync()) after every sync_source_info events.
sync_source_info=10000
If the value of this variable is greater than 0, the MySQL server synchronizes its relay log to disk.
(using fdatasync()) after every sync_relay_log writes to the relay log.
sync_relay_log=10000
If the value of this variable is greater than 0, a replica synchronizes its relay-log.info file to disk.
(using fdatasync()) after every sync_relay_log_info transactions.
sync_relay_log_info=10000
Load mysql plugins at start."plugin_x ; plugin_y".
plugin_load
The TCP/IP Port the MySQL Server X Protocol will listen on.
loose_mysqlx_port=33060
Original: https://www.cnblogs.com/Alone-2021/p/16742885.html
Author: Alone_2021
Title: MySQL日志（二）—— 启动MySQL日志（持续更新，目前仅启动二进制日志）
原创文章受到原创版权保护。转载请注明出处：https://www.johngo689.com/643368/
转载文章受原作者版权保护。转载请注明原作者出处！