Jussi Saurio 2ca388d78d WAL: don't hold shared lock across IO operations ...

Without this change and running:

```
cd stress
cargo run -- --nr-threads=4 -i 1000 --verbose --busy-timeout=0
```

I can produce a deadlock quite reliably.

With this change, I can't.

Even with 5 second busy timeout (the default), the run makes progress although it is slow as hell because of the busy timeout.

2025-10-16 22:00:01 +03:00

..

btree.rs

Merge 'Replace io_yield_many with completion groups' from Pekka Enberg

2025-10-16 17:17:43 +03:00

buffer_pool.rs

Merge 'Run simulator under Miri' from Bob Peterson

2025-10-14 09:26:55 +03:00

checksum.rs

rename checksums tests appropriately

2025-10-13 13:48:07 +05:30

database.rs

rename Completion functions

2025-10-06 11:07:06 -03:00

encryption.rs

Add encryption internals docs

2025-10-02 00:14:28 +05:30

mod.rs

Add checksum module

2025-09-13 11:00:37 +05:30

page_cache.rs

when pwritev fails, clear the dirty pages

2025-10-05 20:02:21 -03:00

pager.rs

Merge 'Replace io_yield_many with completion groups' from Pekka Enberg

2025-10-16 17:17:43 +03:00

slot_bitmap.rs

Rename page -> slot for arenas + buffer pool

2025-08-12 11:36:49 -04:00

sqlite3_ondisk.rs

refactor: remove unsafe reference semantics from RefValue

2025-10-07 10:43:44 -03:00

state_machines.rs

refactor/idx_insert: move seeking to VDBE instead of BTreeCursor

2025-08-19 19:04:42 +03:00

wal.rs

WAL: don't hold shared lock across IO operations

2025-10-16 22:00:01 +03:00