documentation on innodb_flush_log_at_trx_commit_session is incorrect

Bug #635396 reported by Vadim Tkachenko
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Percona Server moved to https://jira.percona.com/projects/PS
Fix Released
High
Fred Linhoss

Bug Description

This variable is defined as

+ "Control innodb_flush_log_at_trx_commit for each sessions. "
+ "The value 0~2 are same meanings to innodb_flush_log_at_trx_commit. "
+ "The value 3 regards innodb_flush_log_at_trx_commit (default).",
+ NULL, NULL, 3, 0, 3, 0);

which contradicts documentation

Changed in percona-server:
status: New → Triaged
importance: Undecided → High
assignee: nobody → Fred Linhoss (fred-linhoss)
milestone: none → 5.1-12.0
Revision history for this message
Baron Schwartz (baron-xaprb) wrote :

I think it is also a bug that a fluent English-speaking person did not edit the definition of the variable:

+ "Control innodb_flush_log_at_trx_commit for each sessions. "
+ "The value 0~2 are same meanings to innodb_flush_log_at_trx_commit. "
+ "The value 3 regards innodb_flush_log_at_trx_commit (default).",
+ NULL, NULL, 3, 0, 3, 0);

It is quite unclear to me what the value 3 actually means.

Changed in percona-server:
status: Triaged → Fix Released
Revision history for this message
Shahriyar Rzayev (rzayev-sehriyar) wrote :

Percona now uses JIRA for bug reports so this bug report is migrated to: https://jira.percona.com/browse/PS-425

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.