Bug #35575 innodb_flush_log_at_trx_commit not actually a dynamic variable

Submitted: 26 Mar 2008 15:01 Modified: 26 Mar 2008 18:50
Reporter: Sheeri Cabral (Candidate Quality Contributor) Email Updates:
Status: Closed Impact on me:
None 
Category:MySQL Server: Documentation Severity:S3 (Non-critical)
Version: OS:Any
Assigned to: CPU Architecture:Any
Tags: 5.0.16-Debian_1glog1-log

[26 Mar 2008 15:01] Sheeri Cabral
Description:
http://dev.mysql.com/doc/refman/5.0/en/server-system-variables.html
Says that 
innodb_flush_log_at_trx_commit is GLOBAL, and "yes" that it's dynamic.  However, it's not actually dynamic:

mysql> set global innodb_flush_log_at_trx_commit = 2;
ERROR 1193 (HY000): Unknown system variable 'innodb_flush_log_at_trx_commit'

I looked around for other folks who may have had this problem, and found this:

http://ircarchive.info/mysql/2007/3/1/28.html

In which HarrisonF (Fisk, presumably) states that it's not a dynamic variable.

How to repeat:
Run

mysql> set global innodb_flush_log_at_trx_commit = 2;

at the command prompt.

Suggested fix:
Fix the documentation to state that it's not a dynamic system variable.
[26 Mar 2008 16:39] Susanne Ebrecht
Thank you for your bug report. This issue has already been fixed in the latest released version of that product, which you can download at

  http://www.mysql.com/downloads/

mysql> select version();

5.0.51a-debug

mysql> set global innodb_flush_log_at_trx_commit = 2;
Query OK, 0 rows affected (0.00 sec)
[26 Mar 2008 18:50] Sheeri Cabral
The documentation page should have a note specifying which version this changed at.

Portions of this website are copyright © 2001, 2002 The PHP Group

Page generated in 0.050 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.