[DOC] innodb_buffer_pool_restore_at_startup
Bug #953304 reported by
Yves Trudeau
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Percona Server moved to https://jira.percona.com/projects/PS |
Fix Released
|
Undecided
|
Hrvoje Matijakovic |
Bug Description
[In:5.5:
The definition at the bottom is wrong, it is a copy of the one for innodb_
"We this variable is set, Percona Server will reload at startup the pages from the last lru dump."
Related branches
lp:~hrvojem/percona-server/bug953304-5.5
- Stewart Smith (community): Approve
-
Diff: 18 lines (+2/-2)1 file modifieddoc/source/management/innodb_lru_dump_restore.rst (+2/-2)
Changed in percona-server: | |
assignee: | nobody → Hrvoje Matijakovic (hrvojem) |
status: | Confirmed → 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.
The documentation is correct, innodb_ buffer_ pool_restore_ at_startup is the 5.5 name for innodb_ auto_lru_ dump, and the renaming happened in 5.5.10-20.1.
The variable (innodb_ buffer_ pool_restore_ at_startup in 5.5 or innodb_ auto_lru_ dump in 5.1) controls both automatic buffer pool dumps and automatic restore on startup. This behavior was a deliberate decision and is described in the manual as well.