[PS8QA] compression dictionary operations not handled under innodb-force-recovery
General
Escalation
General
Escalation
Description
Environment
None
relates to
Smart Checklist
Activity
Show:
Peter Schwaller December 17, 2018 at 1:17 PM
deferred during 8.0 triage meeting
roel.vandepaar December 15, 2018 at 8:15 AM
Ack thank you
Laurynas Biveinis December 14, 2018 at 12:31 PM
This area is not going to result in serious bugs, OK to find them in due course, no need to focus
roel.vandepaar December 14, 2018 at 9:40 AM
one question - you mention that native DD + innodb-force-recovery combination was not handled - are there other situations (think TokuDb, RocksDB, certain recovery operations in innodb-force-recovery mode) in which issues can arise and where we should test things further?
roel.vandepaar December 14, 2018 at 9:33 AM
Agreed, linked as such
Done
Details
Details
Assignee
Satya BodapatiReporter
roel.vandepaarTime tracking
1d 13m logged
Fix versions
Priority
MediumSmart Checklist
Open Smart Checklist
Smart Checklist
Open Smart Checklist
Created December 14, 2018 at 7:01 AM
Updated March 6, 2024 at 12:34 PM
Resolved April 4, 2019 at 11:36 AM
Leads to, on release builds;
And on debug builds to;
This looks to be a regression. 5.7.24-26 for both opt+dbg;
The filter string is very generic ftm. Preferably this bug would be fixed.