Bug #28714 Doc: innodb_safe_binlog and innodb_support_xa
| Submitted: | 28 May 2007 5:41 | Modified: | 30 Aug 2007 16:44 |
|---|---|---|---|
| Reporter: | Yoshiaki Tajika (Basic Quality Contributor) | Email Updates: | |
| Status: | Closed | Impact on me: | |
| Category: | MySQL Server: Documentation | Severity: | S3 (Non-critical) |
| Version: | 5.0, 5.1 | OS: | Any |
| Assigned to: | MC Brown | CPU Architecture: | Any |
[28 May 2007 5:41]
Yoshiaki Tajika
[28 May 2007 7:16]
Sveta Smirnova
Thank you for the report. But there is note "Note: For the greatest possible durability and consistency in a replication setup using InnoDB with transactions, you should use innodb_flush_log_at_trx_commit=1, sync_binlog=1, and, before MySQL 5.0.3, innodb_safe_binlog in your master server my.cnf file. (innodb_safe_binlog is not needed from 5.0.3 on.)" at http://dev.mysql.com/doc/refman/5.0/en/innodb-parameters.html#optvar_innodb_flush_log_at_t... section in the manual.
[28 May 2007 9:22]
Yoshiaki Tajika
Sorry, would you please tell me more? Do you mean, as the current note says, it doesn't matter for durability and consistency in a replication setup whether innodb_support_xa is ON or OFF? But, Heikki Tuuri and Peter Zaitsev say > innodb_support_xa setting to 0 reduces work InnoDB > should do on transaction commit. Binlog can get out of sync at p.31 in the document below. http://www.mysqlperformanceblog.com/files/presentations/UC2007-Innodb-Performance-Optimiza... I'm not asking a technical question, I only want the manual to be valid and adequate.
[1 Jun 2007 6:32]
Sveta Smirnova
Thank you for the additional information. Verified as described.
[30 Aug 2007 16:44]
MC Brown
The documentation has been updated to note that innodb_support_xa should be switched on to ensure synchronization of the data and binary log.
Portions of this website are copyright © 2001, 2002 The PHP Group
Page generated in 0.053 sec. using MySQL 8.4.7-u6-cloud
Timestamp references displayed by the system are UTC.
Content reproduced on this site is the property of the
respective copyright holders.
It is not reviewed in advance
by Oracle and does not necessarily represent the opinion of
Oracle or any other party.