fix innodb_max_purge_lag
Bug #592007 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
|
Wishlist
|
Unassigned | ||
Bug Description
proposes to make
innodb_
replace
if (srv_max_purge_lag > 0
&& !UT_LIST_
to
if (srv_max_purge_lag > 0 ) {
Related branches
lp:~percona-dev/percona-server/release-5.1.48-12-fix576041_592007_607449
- Percona developers: Pending requested
-
Diff: 448 lines (+63/-94)10 files modifiedi_s_innodb_buffer_pool_pages.patch (+24/-67)
innodb_admin_command_base.patch (+1/-1)
innodb_extra_rseg.patch (+3/-3)
innodb_fix_misc.patch (+13/-0)
innodb_lru_dump_restore.patch (+2/-2)
innodb_show_sys_tables.patch (+2/-2)
innodb_split_buf_pool_mutex.patch (+2/-2)
innodb_stats.patch (+3/-3)
mysql-test.diff (+12/-13)
userstat.patch (+1/-1)
| Changed in percona-server: | |
| status: | New → Triaged |
| importance: | Undecided → Wishlist |
| assignee: | nobody → Yasufumi Kinoshita (yasufumi-kinoshita) |
| milestone: | none → 5.1-12.0 |
| Changed in percona-server: | |
| milestone: | 5.1.47-12.0 → 5.1-12.0 |
| Changed in percona-server: | |
| status: | Triaged → Fix Committed |
| Changed in percona-server: | |
| status: | Fix Committed → Fix Released |
Revision history for this message
| Shahriyar Rzayev (rzayev-sehriyar) wrote | #1 |
To post a comment you must log in.
Percona now uses JIRA for bug reports so this bug report is migrated to: https:/