separate doublewrite buffer should use SRV_EXTRA_SYS_SPACE_FIRST_ID instead of SRV_LOG_SPACE_FIRST_ID more
Affects | Status | Importance | Assigned to | Milestone | ||
---|---|---|---|---|---|---|
Percona Server moved to https://jira.percona.com/projects/PS | Status tracked in 5.7 | |||||
5.1 |
Won't Fix
|
Low
|
Unassigned | |||
5.5 |
Triaged
|
Low
|
Unassigned | |||
5.6 |
Invalid
|
Undecided
|
Unassigned | |||
5.7 |
Invalid
|
Undecided
|
Unassigned |
Bug Description
Stock InnoDB uses SRV_LOG_
But not all the code has been converted to use the proper boundary in checks:
1) fil_mutex_
2) fil_assign_
3) fil_set_
4) fil_create_
5) _fil_io
6) fil_aio_wait
7) dict_table_
8) buf_page_
tags: | added: xtradb |
Benign in regular operation, might become fatal or even data corrupting when actual tablespace count approaches the upper bound.