Files
turso/core
Jussi Saurio c30d320cab Fix: read transaction cannot be allowed to start with a stale max frame
If both of the following are true:

1. All read locks are already held
2. The highest readmark of any read lock is less than the committed max frame

Then we must return Busy to the reader, because otherwise they would begin a
transaction with a stale local max frame, and thus not see some committed
changes.
2025-09-11 15:58:13 +03:00
..
2025-09-05 14:56:05 -04:00
2025-06-30 10:01:03 +03:00
2025-08-15 17:08:53 -04:00
2025-01-28 14:55:38 -05:00
2025-09-08 13:18:09 -04:00
2025-06-23 19:52:13 +01:00
2025-08-30 03:10:39 -03:00
2025-01-28 14:55:38 -05:00
2025-09-10 22:44:26 +03:00
2025-06-23 19:52:13 +01:00
2025-06-30 09:54:13 +03:00
2025-09-05 14:56:09 -04:00