sync_binlog
sync_binlog
成都创新互联不只是一家网站建设的网络公司；我们对营销、技术、服务都有自己独特见解，公司采取“创意+综合+营销”一体化的方式为您提供更专业的服务！我们经历的每一步也许不一定是最完美的，但每一步都有值得深思的意义。我们珍视每一份信任，关注我们的网站设计、网站制作质量和服务品质，在得到用户满意的同时，也能得到同行业的专业认可，能够为行业创新发展助力。未来将继续专注于技术创新，服务升级，满足企业一站式成都全网营销推广需求，让再小的品牌网站设计也能产生价值！
| Command-Line Format | --sync-binlog=# | ||
| System Variable | Name | sync_binlog | |
| Variable Scope | Global | ||
| Dynamic Variable | Yes | ||
| Permitted Values (32-bit platforms) | Type | integer | |
| Default | 0 | ||
| Min Value | 0 | ||
| Max Value | 4294967295 | ||
| Permitted Values (64-bit platforms) | Type | integer | |
| Default | 0 | ||
| Min Value | 0 | ||
| Max Value | 4294967295 | ||
If the value of this variable is greater than 0, the MySQL server synchronizes its binary log to disk (using fdatasync()) after sync_binlog commit groups are written to the binary log. The default value of sync_binlog is 0, which does no synchronizing to disk—in this case, the server relies on the operating system to flush the binary log's contents from time to time as for any other file. A value of 1 is the safest choice because in the event of a crash you lose at most one commit group from the binary log. However, it is also the slowest choice (unless the disk has a battery-backed cache, which makes synchronization very fast).
百度翻译：如果这个变量的值大于0，MySQL服务器同步二进制日志到磁盘（使用fdatasync()）后sync_binlog犯组写入二进制日志。sync_binlog的默认值是0，并没有同步在这种情况下，磁盘，服务器依赖于操作系统的二进制日志的内容刷新时间为任何其他文件。一个1的值是最安全的选择，因为在一个崩溃的事件，你失去了最一个提交组从二进制日志。然而，它也是最慢的选择（除非磁盘具有电池备份的高速缓存，这使得同步非常快）。文章标题：sync_binlog
分享路径：http://ybzwz.com/article/igepip.html
