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-02 08:22:36 +02:00
2025-09-05 14:56:05 -04:00
2025-09-10 14:46:07 +03:00
2025-09-05 15:40:45 +03:00
2025-09-10 14:36:02 +03:00
2025-09-10 14:44:54 +03:00
2025-09-10 14:36:02 +03:00
2025-09-10 20:49:30 -03:00
2025-09-11 15:58:13 +03:00
2025-06-30 10:01:03 +03:00
2025-09-10 17:56:22 +03:00
2025-09-11 13:34:07 +03:00
2025-08-15 17:08:53 -04:00
2025-06-29 11:46:18 +03:00
2025-01-28 14:55:38 -05:00
2025-09-10 09:56:12 -04: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-05-13 14:42:12 -04:00
2025-08-28 16:02:41 +03:00
2025-06-23 19:52:13 +01:00
2025-07-30 14:08:33 +03:00
2025-09-11 09:51:46 +03:00
2025-08-05 05:48:29 +02:00
2025-09-02 17:07:38 +02:00
2025-09-10 20:49:30 -03:00
2025-09-11 13:35:36 +03:00
2025-06-30 09:54:13 +03:00
2025-09-05 14:56:09 -04:00