Redundant DB_TABLESPACE_DELETED handling for crash recovery page reads
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
|
Wishlist
|
Unassigned | |||
5.5 |
Won't Fix
|
Wishlist
|
Unassigned | |||
5.6 |
Won't Fix
|
Wishlist
|
Unassigned | |||
5.7 |
Fix Released
|
Wishlist
|
Laurynas Biveinis | |||
Percona XtraBackup moved to https://jira.percona.com/projects/PXB | ||||||
2.0 |
Invalid
|
Wishlist
|
Unassigned | |||
2.1 |
Invalid
|
Wishlist
|
Unassigned |
Bug Description
XtraDB and XtraBackup patch buf_read_page_low() and buf_read_
I believe this patch is not required anymore, or never was required in the first place. It is possible that it appeared to be required for XtraBackup before the recent data dictionary handling improvements.
[10 Feb 11:13] Laurynas Biveinis
I don't see how the described situation may ever occur, at least with the current trunks. The patch handles the situation of recovery trying to read a page from a deleted tablespace into the buffer pool. But recovery initializes the fil_space structures by looking at the actual ibds on the disk (fil_load_
Thus a tablespace should somehow disappear between the fil_load_
I'd replace the Yasufumi's patch with something like
ut_ad(!
to be sure.
5.6 affected too, the original patch is already merged there.