Files
turso/core
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
..
2025-10-06 13:21:45 +04:00
2025-09-24 18:06:55 -03:00
2025-06-30 10:01:03 +03:00
fmt
2025-10-14 22:22:14 +04:00
2025-10-16 01:22:54 -03:00
2025-10-07 16:22:20 -04:00
2025-01-28 14:55:38 -05:00
2025-10-16 11:26:50 +03:00
2025-09-30 14:52:59 +04:00
2025-10-09 19:00:40 +03:00
2025-09-22 16:37:31 +03:00
2025-10-15 11:48:24 +03:00
2025-06-30 09:54:13 +03:00
2025-09-23 14:22:02 -04:00