tursodatabase / tursodatabase/libsql
Switch to locking_mode EXCLUSIVE in libSQL server?
Open
Nobody has claimed this yet.
enhancement
help wanted
question
- Dominant language
- C
- Stars
- 17.2k
- Forks
- 531
- Avg merge
- 1h 12m
- Merged PRs (30d)
- 1
Description
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.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reviewing SQLite's locking_mode behavior and the libSQL server's database-opening path, then assess the read-performance and locking implications of changing the default. Done means the project has a tested, documented decision about whether to use EXCLUSIVE locking and any resulting behavior is covered by relevant tests.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- c, sqlite
- Domain
- databases
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 42/100