Lines Matching refs:aReadMark

248 # running recovery, it fails to obtain a lock on an aReadMark[] slot
344 # kind of read lock (on aReadMark[0]). This set of test cases tests the 
350 #     acquire a different read-lock (not aReadMark[0]) and read the new
353 #   + The attempt to obtain the lock on aReadMark[0] fails with SQLITE_BUSY.
381 # Test case 3.6.1.4 has [db] attempt a read-lock on aReadMark[0]. But
388     # This is the callback for [db] to obtain the read lock on aReadMark[0].
405 # aReadMark[0]. Test this by demonstrating that the read-lock is preventing
418 # aReadMark[0], it would have been possible to wrap the log in 3.6.1.5.
492 # lock on aReadMark[x], where x>0. The following test cases experiment
501 #   + The value in the aReadMark[x] slot has been modified since it was
564 # an aReadMark[] slot that is already set to the mxFrame value for the
566 # exclusive lock on an aReadMark[] slot for the purposes of modifying
571 # on any aReadMark[] slot (because there are already several readers),