summaryrefslogtreecommitdiff
path: root/packaging
diff options
context:
space:
mode:
authorAditya A <aditya.a@oracle.com>2013-07-05 14:30:15 +0530
committerAditya A <aditya.a@oracle.com>2013-07-05 14:30:15 +0530
commit37d9d2439208c42d00189f46b7d4fef1bfa0cf7b (patch)
tree0efdf9db38f0c7a4e2b17d96d3f24738ea44f337 /packaging
parent18d34a47a4c455c55a8249012aeaf7bb0fc05a20 (diff)
downloadmariadb-git-37d9d2439208c42d00189f46b7d4fef1bfa0cf7b.tar.gz
Bug#17033706 SINCE 5.5.32 & 5.6.12, INNODB CANT START WITH OWN
MULTI-FILE TABLESPACE ANALYSIS -------- When a tablespace has multiple data files, InnoDB fails to open the tablespace. This is because for each ibd file, the first page is checked.But the first page of all ibd file need not be the first page of the tablespace. Only the first page of the tablespace contains the tablespace header. When we check the first page of an ibd file that is not the first page of the tablespace, then the "tablespace flags" is not really available.This was wrongly used to check if a page is corrupt or not. FIX --- Use the tablespace flags only if the page number is 0 in a tablespace. [Approved by Inaam rb#2836 ]
Diffstat (limited to 'packaging')
0 files changed, 0 insertions, 0 deletions