MySQL的my-innodb-heavy-4G.ini配置文件的翻译

我根据MySQL配置文件的英文文档说明，在根据自己所学的知识，使用有道词典对不懂的单词进行了查询，一个一个翻译出来的。有的专业术语翻译的不好，我使用了英文进行标注，例如主机(master)和副机(slave hosts)，不知道如何翻译，所有在翻译后面加上了英文标识。

下面是这个MySQL的my-innodb-heavy-4G.ini配置文件的中英对照版，如果有些地方解释的不对，希望大神可以指正。

所有以"注："开头的都是翻译部分。

  1 #BEGIN CONFIG INFO    
  2 #DESCR: 4GB RAM, InnoDB only, ACID, few connections, heavy queries
  3 #TYPE: SYSTEM
  4 #END CONFIG INFO
  5 
  6 #注:这个用于4G的内存，并且只能用于InnoDB模式，支持事务的ACID，很少的连接数，很大的查询数
  7 
  8 
  9 #
 10 # This is a MySQL example config file for systems with 4GB of memory
 11 # running mostly MySQL using InnoDB only tables and performing complex
 12 # queries with few connections.
 13 # 
 14 
 15 #注:这是MySQL的一个样例的配置文件，要求系统有至少4G的内存，运行MySQL使用InnoDB模式运行复杂的连接但是连接数较少
 16 
 17 # MySQL programs look for option files in a set of
 18 # locations which depend on the deployment platform.
 19 # You can copy this option file to one of those
 20 # locations. For information about these locations, see:
 21 # http://dev.mysql.com/doc/mysql/en/option-files.html
 22 
 23 #注:MySQL程序将会寻找参数(配置)文件在一系列的地方,这个依赖MySQL的运行的平台和安装情况，你可以复制这些文件
 24 #到MySQL查找配置的文件的路径。如果你想知道更多的信息，可以参考： http://dev.mysql.com/doc/mysql/en/option-files.html
 25 
 26 # In this file, you can use all long options that a program supports.
 27 # If you want to know which options a program supports, run the program
 28 # with the "--help" option.
 29 #
 30 
 31 #注:在这个配置文件中，你可以使用所有被MySQL程序支持的长参数，如果你想知道有那些参数被MySQL支持，你可以使用如下命令
 32 # mysql --help 或者  man mysql-5.1.72/support-files/my-innodb-heavy-4G.cnf
 33 
 34 # More detailed information about the individual options can also be
 35 # found in the manual.
 36 #
 37 
 38 #注：更多详细的信息关于个别的参数可以参考参考手册
 39 
 40 #
 41 # The following options will be read by MySQL client applications.
 42 # Note that only client applications shipped by MySQL are guaranteed
 43 # to read this section. If you want your own MySQL client program to
 44 # honor these values, you need to specify it as an option during the
 45 # MySQL client library initialization.
 46 #
 47 
 48 #注：接下来的参数将会被MySQL客户端应用读取。记住只有那些被MySQL服务端授权的客户端才会保证去读取到这些参数
 49 #如果你想让你自己的MySQL客户端去读取这些参数，你需要指定这个作为一个选项在你的MySQL客户端lib库初始化的时候
 50 
 51 [client]    #客户端参数配置
 52 #password    = [your_password]    #你自己的密码
 53 port        = 3306            #数据库的端口为3306
 54 socket        = /application/mysql5.1.72/tmp/mysql.sock    #指定socket路径，我也不知道什么意思
 55 
 56 # *** Application-specific options follow here ***
 57 
 58 #注下面是MySQL服务端参数配置
 59 
 60 #
 61 # The MySQL server
 62 #
 63 [mysqld]
 64 
 65 # generic configuration options
 66 port        = 3306        #数据库服务端端口为3306
 67 socket        = /application/mysql5.1.72/tmp/mysql.sock    #指定socket路径
 68 
 69 # back_log is the number of connections the operating system can keep in
 70 # the listen queue, before the MySQL connection manager thread has
 71 # processed them. If you have a very high connection rate and experience
 72 # "connection refused" errors, you might need to increase this value.
 73 # Check your OS documentation for the maximum value of this parameter.
 74 # Attempting to set back_log higher than your operating system limit
 75 # will have no effect.
 76 back_log = 50
 77 
 78 #注:back_log 是一个数值，在数据库连接管理器处理这些队列之前，操作系统可以保持监听队列的数量。
 79 #如果你的数据库服务有一个很高的连接数并且有连接拒绝的经历，你可以增大这个值。你需要检查你的操作系统
 80 #的文件系统对这个参数的最大支持。如果你设定的值超过操作系统的最大值，那么这个值将无效
 81 
 82 
 83 # Don't listen on a TCP/IP port at all. This can be a security
 84 # enhancement, if all processes that need to connect to mysqld run
 85 # on the same host.  All interaction with mysqld must be made via Unix
 86 # sockets or named pipes.
 87 # Note that using this option without enabling named pipes on Windows
 88 # (via the "enable-named-pipe" option) will render mysqld useless!
 89 #skip-networking
 90 
 91 #注:skip-networking 这个参数是一个属性，没有值。把注解去掉即生效。这个参数的用途为：
 92 #不监听TCP/IP的端口。这是一个增加安全的参数，如果所有的连接MySQL的程序都来自相同的主机。
 93 #这样，所有与MySQL服务器的连接都需要在通道或者管道中进行
 94 #记住:使用这个参数不能使用管道早Windows中
 95 
 96 
 97 # The maximum amount of concurrent sessions the MySQL server will
 98 # allow. One of these connections will be reserved for a user with
 99 # SUPER privileges to allow the administrator to login even if the
100 # connection limit has been reached.
101 max_connections = 100
102 
103 #注：MySQL允许的最大连接数。在这些连接中，始终会为超级管理员保留一个连接，即使所有的连接已经达到上限
104 
105 # Maximum amount of errors allowed per host. If this limit is reached,
106 # the host will be blocked from connecting to the MySQL server until
107 # "FLUSH HOSTS" has been run or the server was restarted. Invalid
108 # passwords and other errors during the connect phase result in
109 # increasing this value. See the "Aborted_connects" status variable for
110 # global counter.
111 max_connect_errors = 10
112 
113 #注：每个客户端运行的最大的错误数。如果错误的数量到达上限，这个客户端将会被阻塞去连接数据库直到刷新客户端
114 #或者重新启动服务器。无效的密码或者其他的连接错误都算作错误，会增加这个值。可以参考Aborted_connects的状态
115 #来查看全局的计数器
116 
117 # The number of open tables for all threads. Increasing this value
118 # increases the number of file descriptors that mysqld requires.
119 # Therefore you have to make sure to set the amount of open files
120 # allowed to at least 4096 in the variable "open-files-limit" in
121 # section [mysqld_safe]
122 table_open_cache = 2048
123 
124 #注：这个值代表着所有对外开放的数据表的数量。增加这个值将会增加MySQL所需要的文件描述符
125 #因此你需要去设置"open-files-limit"的值至少为4096在MySQL安全的配置文件中，你可以看到这个值在本文的最后
126 
127 # Enable external file level locking. Enabled file locking will have a
128 # negative impact on performance, so only use it in case you have
129 # multiple database instances running on the same files (note some
130 # restrictions still apply!) or if you use other software relying on
131 # locking MyISAM tables on file level.
132 #external-locking
133 
134 #注：external-locking为外部文件锁的意思，可用的外部文件锁。如果使用外部文件锁将会对MySQL的性能有消极影响。
135 #因此使用外部文件锁当你有多重的数据库实例运行在相同的文件中(记住一些限制任然是有用的)或者可用使用一些依赖MyISAM的外部锁软件
136 
137 
138 # The maximum size of a query packet the server can handle as well as
139 # maximum query size server can process (Important when working with
140 # large BLOBs).  enlarged dynamically, for each connection.
141 max_allowed_packet = 16M
142 
143 #注：MySQL查询包的最大值或者是处理查询的最大值,(这个属性非常重要，如果你操作很大的二进制对象的数据的时候)
144 #这个值可以对每个线程进行动态的扩大
145 
146 # The size of the cache to hold the SQL statements for the binary log
147 # during a transaction. If you often use big, multi-statement
148 # transactions you can increase this value to get more performance. All
149 # statements from transactions are buffered in the binary log cache and
150 # are being written to the binary log at once after the COMMIT.  If the