| 2013-12-26 14:34:39 |
Jaime Crespo |
bug |
|
|
added bug |
| 2013-12-27 04:20:04 |
Laurynas Biveinis |
nominated for series |
|
percona-server/5.1 |
|
| 2013-12-27 04:20:04 |
Laurynas Biveinis |
bug task added |
|
percona-server/5.1 |
|
| 2013-12-27 04:20:04 |
Laurynas Biveinis |
nominated for series |
|
percona-server/5.5 |
|
| 2013-12-27 04:20:04 |
Laurynas Biveinis |
bug task added |
|
percona-server/5.5 |
|
| 2013-12-27 04:20:04 |
Laurynas Biveinis |
nominated for series |
|
percona-server/5.6 |
|
| 2013-12-27 04:20:04 |
Laurynas Biveinis |
bug task added |
|
percona-server/5.6 |
|
| 2013-12-27 04:20:27 |
Laurynas Biveinis |
percona-server/5.1: importance |
Undecided |
Medium |
|
| 2013-12-27 04:20:29 |
Laurynas Biveinis |
percona-server/5.5: importance |
Undecided |
Medium |
|
| 2013-12-27 04:20:31 |
Laurynas Biveinis |
percona-server/5.6: importance |
Undecided |
Medium |
|
| 2013-12-27 04:20:37 |
Laurynas Biveinis |
percona-server/5.1: assignee |
|
Hrvoje Matijakovic (hrvojem) |
|
| 2013-12-27 04:20:41 |
Laurynas Biveinis |
percona-server/5.5: assignee |
|
Hrvoje Matijakovic (hrvojem) |
|
| 2013-12-27 04:20:46 |
Laurynas Biveinis |
percona-server/5.6: assignee |
|
Hrvoje Matijakovic (hrvojem) |
|
| 2013-12-27 04:20:52 |
Laurynas Biveinis |
tags |
|
doc |
|
| 2013-12-27 04:20:58 |
Laurynas Biveinis |
percona-server/5.1: status |
New |
Triaged |
|
| 2013-12-27 04:21:00 |
Laurynas Biveinis |
percona-server/5.5: status |
New |
Triaged |
|
| 2013-12-27 04:21:03 |
Laurynas Biveinis |
percona-server/5.6: status |
New |
Triaged |
|
| 2013-12-27 09:34:12 |
Jaime Crespo |
description |
This and the same section on 5.5 is poorly written and has some documentation bugs:
http://www.percona.com/doc/percona-server/5.6/scalability/innodb_io.html#innodb_use_global_flush_log_at_trx_commit
In summary:
* The feature doc is difficult to understand, and overuses "GLOBAL" when it means "session as if it was set globally"
* I think it has some erroneous information: wrong quoted example and the session variable can always be set, but (hopefully) it will have no effect
* The feature is not documented in any other place, and it requires further discussion than simple parameters settings
I have written an alternative version (please check validity) to at least change the current information:
---------------
This variable is used to enable or disable the effect of the per session value of innodb_flush_log_at_trx_commit.
If the global variable innodb_use_global_flush_log_at_trx_commit is set to 1 (True), the session will use always use the current global value of innodb_flush_log_at_trx_commit. This is the default value. Under this mode, changing the session variable for innodb_flush_log_at_trx_commit will have not effect for upstream compatibility.
If the global variable innodb_use_global_flush_log_at_trx_commit is set to 0 (False), the user can modify the MySQL commit durability per session, using:
SET SESSION innodb_flush_log_at_trx_commit=N
This change will only affect the transactions in the session where it has changed, while the rest will keep the global innodb_flush_log_at_trx_commit value unless similarly changed. |
This and the same section on 5.5 is poorly written and has some documentation bugs:
http://www.percona.com/doc/percona-server/5.6/scalability/innodb_io.html#innodb_use_global_flush_log_at_trx_commit
In summary:
* The feature doc is difficult to understand, and overuses "GLOBAL" when it means "session as if it was set globally"
* I think it has some erroneous information: wrong quoted example and the session variable can always be set, but (hopefully) it will have no effect
* The feature is not documented in any other place, and it requires further discussion than simple parameters settings
I have written an alternative version (please check validity) to at least change the current information:
---------------
This variable is used to enable or disable the effect of the per session value of innodb_flush_log_at_trx_commit.
If the global variable innodb_use_global_flush_log_at_trx_commit is set to 1 (True), the session will use always use the current global value of innodb_flush_log_at_trx_commit. This is the default value.
Under this mode, changing the session variable for innodb_flush_log_at_trx_commit will have no effect for upstream compatibility.
If the global variable innodb_use_global_flush_log_at_trx_commit is set to 0 (False), the user can modify the MySQL commit durability per session, using:
SET SESSION innodb_flush_log_at_trx_commit=N
This change will only affect the transactions in the session where it has changed, while the rest will keep the global innodb_flush_log_at_trx_commit value unless similarly changed. |
|
| 2016-03-24 15:22:01 |
Laurynas Biveinis |
nominated for series |
|
percona-server/5.7 |
|
| 2016-03-24 15:22:01 |
Laurynas Biveinis |
bug task added |
|
percona-server/5.7 |
|
| 2016-03-24 15:22:17 |
Laurynas Biveinis |
percona-server/5.1: status |
Triaged |
Won't Fix |
|
| 2017-08-01 06:48:01 |
Hrvoje Matijakovic |
percona-server/5.1: assignee |
Hrvoje Matijakovic (hrvojem) |
Borys Belinsky (borys-belinsky-percona) |
|
| 2017-08-01 06:48:05 |
Hrvoje Matijakovic |
percona-server/5.5: assignee |
Hrvoje Matijakovic (hrvojem) |
Borys Belinsky (borys-belinsky-percona) |
|
| 2017-08-01 06:48:09 |
Hrvoje Matijakovic |
percona-server/5.6: assignee |
Hrvoje Matijakovic (hrvojem) |
Borys Belinsky (borys-belinsky-percona) |
|
| 2017-08-01 06:48:13 |
Hrvoje Matijakovic |
percona-server/5.7: assignee |
Hrvoje Matijakovic (hrvojem) |
Borys Belinsky (borys-belinsky-percona) |
|
