tdb2: fix two transaction bugs.
One but were we didn't update the map_size if we expanded the transaction but didn't create a new recovery area (most easily reproduced by setting the TDB_NOSYNC flag). Another out-by-one bug in transaction_direct where we would give read-access to the underlying file despite the last block having been modified. Both these were found by tdbtorture.
Showing
Please register or sign in to comment