Change behavior of innodb_flush_log_at_trx_commit_session variable
Bug #635399 reported by
Vadim Tkachenko
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Percona Server moved to https://jira.percona.com/projects/PS |
Fix Released
|
High
|
Unassigned |
Bug Description
1. We need to check if we can define innodb_
SET SESSION innodb_
2. If that is not possible we need to change innodb_
New behavior :
-It accepts only 0-2 values.
-when connection starts innodb_
Changed in percona-server: | |
status: | New → Triaged |
importance: | Undecided → High |
assignee: | nobody → Yasufumi Kinoshita (yasufumi-kinoshita) |
milestone: | none → 5.1-12.0 |
Changed in percona-server: | |
milestone: | 5.1-12.0 → 5.1.53-12.4 |
Changed in percona-server: | |
milestone: | 5.1.53-12.4 → 5.5-20beta |
Changed in percona-server: | |
status: | Triaged → In Progress |
Changed in percona-server: | |
status: | In Progress → Fix Committed |
Changed in percona-server: | |
status: | Fix Committed → Fix Released |
To post a comment you must log in.
innodb_ flush_log_ at_trx_ commit is currently global variable.
If it changes to session value, the compatibility is broken.
For session variable, the GLOBAL is only default value when starting session.
I think you ignore the compatibility. I cannot accept it.