Pere Diaz Bou cb4efdbc19 Merge 'LimboRwLock write and read lock fixes' from Pere Diaz Bou ...

* `write` was returning `true` even though it shouldn't because it
should return `false` in case it was already acquired.
* `read` theoritically can increase `nread` after another thread calls
`unlock` between first lock load and increase of `nread`. So it looks
something like this:
                  1. THREAD  1: read()
                  2. THREAD 2: get lock = `SHARED_LOCK`
                  3. THREAD 1: unlock -> lock is now `NO_LOCK`
                  4. THREAD 2: increase nread, return true.
    This is obviously wrong because `nreads` will be ` > 0 ` but `lock`
is `NO_LOCK`

Closes #1676

2025-06-09 16:15:46 +02:00

..

btree.rs

addresses comment https://github.com/tursodatabase/limbo/pull/1600#discussion_r2115796655 by @jussisaurio

2025-06-06 23:14:25 +05:30

buffer_pool.rs

core: Move buffer_pool.rs to storage module

2024-08-01 11:53:14 +03:00

database.rs

core/io: Switch to Arc<Completion>

2025-05-27 11:28:49 +03:00

mod.rs

Minor improvements and cleanups in btree

2025-03-01 15:48:42 -05:00

page_cache.rs

remove dumb comment from pagecachekey

2025-05-29 14:12:16 +02:00

pager.rs

Persisting database header and pointer map page to cache

2025-06-06 23:14:25 +05:30

sqlite3_ondisk.rs

Addresses comment https://github.com/tursodatabase/limbo/pull/1600#discussion_r2115842804 by @jussisaurio

2025-06-06 23:14:25 +05:30

wal.rs

fix race condition with read lock in between unlock

2025-06-06 12:16:41 +02:00