What is LSM, and Why LSM? Jungle 发布于 2024-08-24 包括在 DatabaseWhat is LSM, and Why LSM? 本文章是对LSM的基本介绍 LSM trees全称为Log-structured merge trees,是一种用于KV存储引擎的数据结构,它被广泛
数据库SQL引擎基础(OceanBase-MiniOB) Jungle 发布于 2024-07-21 包括在 Database数据库SQL引擎基础$(OceanBase-MiniOB)$ 引擎架构概览 MySQL的引擎架构(红框) OceanBase引擎架构 一条SQL语句
CMU 15-445 Lecture #24: Distributed OLAP Databases Jungle 发布于 2024-06-18 包括在 CMU 15-445 Database SystemsCMU 15-445 Database Systems Lecture #24: Distributed OLAP Databases Decision Support Systems OLAP其他称呼,就是分析数据进行公司的决策分析的 两种“数据”架构 Star Schema Snowflake Schema Star Schema 一张核心表,通过外键连接到外面的表 下面
CMU 15-445 Lecture #23: Distributed OLTP Databases Jungle 发布于 2024-06-17 包括在 CMU 15-445 Database SystemsCMU 15-445 Database Systems Lecture #23: Distributed OLTP Databases We have not discussed how to ensure that all nodes agree to commit a txn and then to make sure it does commit if the DBMS decides it should. → What happens if a node fails? → What happens if messages show up late? → What happens if the system does not wait for every node to agree to commit? Atomic
CMU 15-445 Lecture #22: Introduction to Distributed Databases Jungle 发布于 2024-06-17 包括在 CMU 15-445 Database SystemsCMU 15-445 Database Systems Lecture #22: Introduction to Distributed Databases Introduction Distributed DBMSs 辨析概念:Parallel DBMSs vs Distributed DBMSs Parallel DBMSs: Nodes are physically close to each other. Nodes connected with high-speed LAN(Local Area Network). Communication cost is assumed to be small. Distributed DBMSs: Nodes can be far from each other. Nodes connected using public network. Communication cost and
CMU 15-445 Lecture #21: Database Crash Recovery Jungle 发布于 2024-04-22 包括在 CMU 15-445 Database SystemsCMU 15-445 Database Systems Lecture #21: Database Crash Recovery Crash Recovery The DBMS relies on its recovery algorithms to ensure database consistency(C), transaction atomicity(A), and durability(D) despite failures. Each recovery algorithm is comprised of two parts: Actions during normal transaction processing to ensure that the DBMS can recover from a failure Actions after a failure to recover the database to a state that ensures the atomicity, consistency, and durability of
CMU 15-445 Lecture #20: Database Logging Jungle 发布于 2024-04-21 包括在 CMU 15-445 Database SystemsCMU 15-445 Database Systems Lecture #20: Database Logging Crash Recovery 情景:数据库运行到一半没电了 Recovery algorithms are techniques to ensure database consistency(C), transaction atomicity(A), and durability(D) despite failures(example no power) The key primitives that used in recovery algorithms are UNDO and REDO. Not all algorithms use both primitives. UNDO: The process of removing the effects of an incomplete or aborted
CMU 15-445 Lecture #19: Multi-Version Concurrency Control Jungle 发布于 2024-04-21 包括在 CMU 15-445 Database SystemsCMU 15-445 Database Systems Lecture #19: Multi-Version Concurrency Control Multi-Version Concurrency Control 常常作为2PL和T/O的辅助手段 The DBMS maintains multiple physical versions of a single logical object in the database(维护多个历史版本(像git)) When a txn writes to
CMU 15-445 Lecture #18: Timestamp Ordering Concurrency Control Jungle 发布于 2024-04-20 包括在 CMU 15-445 Database SystemsCMU 15-445 Database Systems Lecture #18: Timestamp Ordering Concurrency Control Timestamp Ordering Concurrency Control 纯用锁很影响性能,锁是一个悲观的方法 乐观的方法:用时间戳 If $TS(T_i) < TS(T_j)$, then the DBMS must ensure that the execution schedule is equivalent to the serial schedule where $T_i$appears before $T_j$ . Multiple implementation strategies: →
CMU 15-445 Lecture #17: Two-Phase Locking Jungle 发布于 2024-04-19 包括在 CMU 15-445 Database SystemsCMU 15-445 Database Systems Lecture #17: Two-Phase Locking Transaction Locks 在操作数据的时候通过DBMS的锁管理器给数据上一把锁,这样就可以避免并发的数据竞争问题 但是这个锁怎么加怎么解的方案需要设