-
Type: Technical Debt
-
Resolution: Gone away
-
Priority: Major - P3
-
None
-
Affects Version/s: None
-
Component/s: None
-
8
-
Storage 2017-10-23, Storage 2017-11-13, Storage 2017-12-04, Storage 2018-01-01, 2023-07-25 Absolute unit, StorEng - 2023-08-08, ASeasonTooMany-2023-08-22, BermudaTriangle- 2023-09-05
While creating the slides on schema ops and going through the operations for rename, I believe I found a hole where a crash during rename at the wrong time could leave the database unrecoverable where the files and metadata are out of sync.