Misleading innodb_extra_rsegments documentation
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Percona Server moved to https://jira.percona.com/projects/PS |
Fix Released
|
Undecided
|
Hrvoje Matijakovic | ||
5.1 |
Fix Released
|
Undecided
|
Hrvoje Matijakovic |
Bug Description
Original report by Simon Kuhn, verified by me:
According to the Percona docs, innodb_
With Percona Server 5.1.58-rel12.9 (and also 5.1.62-rel13.2), I've done the following:
- Modify /etc/mysql/my.conf:
[mysqld]
innodb_
mysql> set global innodb_
/etc/init.d/mysql restart
mysql> show global variables like 'innodb_
+------
| Variable_name | Value |
+------
| innodb_
+------
1 row in set (0.00 sec)
mysql> SELECT COUNT(*) FROM information_
+----------+
| COUNT(*) |
+----------+
| 1 |
+----------+
1 row in set (0.00 sec)
Related branches
- Alexey Kopytov (community): Approve
-
Diff: 126 lines (+19/-29)6 files modifieddoc/source/diagnostics/innodb_stats.rst (+2/-3)
doc/source/diagnostics/mysql_syslog.rst (+1/-1)
doc/source/diagnostics/slow_extended.rst (+2/-2)
doc/source/installation/apt_repo.rst (+12/-0)
doc/source/reliability/innodb_corrupt_table_action.rst (+0/-23)
doc/source/scalability/innodb_extra_rseg.rst (+2/-0)
Changed in percona-server: | |
status: | Confirmed → In Progress |
Changed in percona-server: | |
status: | In Progress → Fix Committed |
Changed in percona-server: | |
status: | Fix Committed → Fix Released |
That is expected behavior. The documentation is wrong. extra_rsegments working.
For 5.1 you need to create database from zero to have innodb_