tursodatabase/libsql

Switch to locking_mode EXCLUSIVE in libSQL server?

Open

#1,630 建立於 2024年8月3日

在 GitHub 查看
 (2 留言) (1 反應) (0 負責人)C (16,744 star) (490 fork)batch import
enhancementhelp wantedquestion

描述

SQLite acquires a POSIX advisory lock by default for every read transaction. Let's consider switching to PRAGMA locking_mode=EXCLUSIVE to make SQLite acquire the POSIX advisory lock when a database file is opened, which improves read performance.

貢獻者指南

技術棧
c
領域
backenddatabaseperformance
議題類型
performance
難度面向新貢獻者的預計實作難度，1 表示很小改動，5 表示專家級工作。
3
預計時間有經驗貢獻者完成調查、實作、測試並準備 pull request 的粗略時間範圍。
1-2 days
活動狀態議題目前的可參與程度：新鮮、活躍、陳舊、阻塞或等待維護者輸入。
fresh
清晰度議題是否清楚說明預期改動、驗收標準和下一步。
clear
前置要求
C programmingSQLite internalsPOSIX advisory locks
新手友善度1-100 的估計分數，表示該議題對首次貢獻者的友善程度。
45
研究方向
Investigate where the SQLite database connection is opened in libSQL server code (likely in files handling database initialization). Evaluate the impact of switching to PRAGMA locking mode=EXCLUSIVE on read performance and compatibility with concurrent writes. Consider any trade offs and test with existing benchmarks.
Switch to locking_mode EXCLUSIVE in libSQL server? · tursodatabase/libsql#1630 | Good First Issue