mirror of
https://github.com/aljazceru/turso.git
synced 2025-12-25 12:04:21 +01:00
- transaction which was started with max_frame = 0 and max_frame_read_lock_index = 0 can write to the WAL and in this case it needs to read data back from WAL - without cache spilling its hard to reproduce this issue for the turso-db now, but I stumbled into this issue with sync-engine which do weird stuff with the WAL which "simulates" cache spilling behaviour to some extent