Searched refs:aReadMark (Results 1 – 3 of 3) sorted by relevance
248 # running recovery, it fails to obtain a lock on an aReadMark[] slot344 # 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 new381 # Test case 3.6.1.4 has [db] attempt a read-lock on aReadMark[0]. But405 # aReadMark[0]. Test this by demonstrating that the read-lock is preventing418 # 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 experiment501 # + The value in the aReadMark[x] slot has been modified since it was564 # an aReadMark[] slot that is already set to the mxFrame value for the566 # exclusive lock on an aReadMark[] slot for the purposes of modifying[all …]
401 # lappend expected_locks {4 4 lock exclusive} ;# Lock all aReadMark[]402 lappend expected_locks {4 1 lock exclusive} ;# Lock aReadMark[1]403 lappend expected_locks {4 1 unlock exclusive} ;# Unlock aReadMark[1]411 # lappend expected_locks {4 4 unlock exclusive} ;# Unlock all aReadMark[] 413 lappend expected_locks {3 1 lock exclusive} ;# Lock aReadMark[0]414 lappend expected_locks {3 1 unlock exclusive} ;# Unlock aReadMark[0]684 # aReadMark[1] slot with the current mxFrame value. Followed by694 # aReadMark[1] is already set to mxFrame. So just READMARK1_READ
396 u32 aReadMark[WAL_NREADER]; /* Reader marks */ member1408 pInfo->aReadMark[0] = 0; in walIndexRecover()1413 pInfo->aReadMark[i] = pWal->hdr.mxFrame; in walIndexRecover()1415 pInfo->aReadMark[i] = READMARK_NOT_USED; in walIndexRecover()1999 pInfo->aReadMark[1] = 0; in walRestartHdr()2001 assert( pInfo->aReadMark[0]==0 ); in walRestartHdr()2072 u32 y = AtomicLoad(pInfo->aReadMark+i); in walCheckpoint()2078 AtomicStore(pInfo->aReadMark+i, iMark); in walCheckpoint()2840 u32 thisMark = AtomicLoad(pInfo->aReadMark+i); in walTryBeginRead()2853 AtomicStore(pInfo->aReadMark+i,mxFrame); in walTryBeginRead()[all …]