斯坦福_数据库系统实现_Notes03.ppt

CS 245 Notes 3 * Block Deletion Rx CS 245 Notes 3 * Options: (a) Immediately reclaim space (b) Mark deleted CS 245 Notes 3 * Options: (a) Immediately reclaim space (b) Mark deleted May need chain of deleted records (for re-use) Need a way to mark: special characters delete field in map CS 245 Notes 3 * As usual, many tradeoffs... How expensive is to move valid record to free space for immediate reclaim? How much space is wasted? e.g., deleted records, delete fields, free space chains,... CS 245 Notes 3 * Dangling pointers Concern with deletions R1 ? CS 245 Notes 3 * Solution #1: Do not worry CS 245 Notes 3 * E.g., Leave “MARK” in map or old location Solution #2: Tombstones CS 245 Notes 3 * E.g., Leave “MARK” in map or old location Solution #2: Tombstones Physical IDs A block This space This space can never re-used be re-used CS 245 Notes 3 * Logical IDs ID LOC 7788 map Never reuse ID 7788 nor space in map... E.g., Leave “MARK” in map or old location Solution #2: Tombstones CS 245 Notes 3 * Easy case: records not in sequence ? Insert new record at end of file or in deleted slot ? If records are variable size, not as easy... Insert CS 245 Notes 3 * Hard case: records in sequence ? If free space “close by”, not too bad... ? Or use overflow idea... Insert CS 245 Notes 3 * Interesting problems: How much free space to leave in each block, track, cylinder? How often do I reorganize file + overflow? CS 245 Notes 3 * Free space CS 245 Notes 3 * DB features needed Why LRU may be bad Read Pinned blocks Textbook! Forced output Double buffering Swizzling Buffer Management in Notes02 CS 245 Notes 3 * Swizzling Memory Disk Rec A block 1 block 2 block 1 CS 245 Notes 3 * Swizzling Memory Disk Rec A block 1 Rec A block 2 block 2 block 1 CS 245 Notes 3 * Row vs Column Store So far we assumed that fields of a record are stored contiguously (row store)... Another option is to store like fields together (