Jussi Saurio 9234ef86ae mvcc: fix two sources of panic ...

1. commit state machine was assuming that begin_write_tx() cannot
fail, but it can fail if there is another tx that is not using
BEGIN CONCURRENT.

2. if a brand new non-CONCURRENT transaction attempts to start
exclusive transaction but fails with Busy, we must end the read
pager read tx it just started, because otherwise the next time
it attempts to do something it will panic with:

"cannot start a new read tx without ending an existing one"

2025-09-15 10:59:44 +03:00

..

mod.rs

mvcc: fix two sources of panic

2025-09-15 10:59:44 +03:00

tests.rs

fix mvcc rollback

2025-09-15 09:29:08 +03:00