Lines Matching full:writer
7319 ** database writer and all readers are reading from the most recent database
7347 ** "writer" lock on the database file. If the writer lock cannot be obtained
7348 ** immediately, and a busy-handler is configured, it is invoked and the writer
7352 ** the writer lock is obtained or while waiting for database readers, the
9402 ** There can only be one writer. A RESERVED_LOCK is obtained by locking
9408 ** which means we can use reader/writer locks. When reader/writer locks
38417 /* Obtain or release the WRITER lock. */
45718 ** the writer will first "reset" the WAL back to the beginning and start
46358 /* If the entry in aPgno[] is already set, then the previous writer
47339 ** with a writer. So get a WRITE lock and try again.
47581 ** that the log file may have been wrapped by a writer, or that frames
47791 ** There can only be a single writer active at a time.
47804 /* Only one writer allowed at a time. Get the write lock. Return
47914 ** was started. Right after that, the writer decided to wrap around
48084 WalWriter w; /* The writer */
48295 ** If the writer lock cannot be obtained, then a passive checkpoint is
48296 ** run instead. Since the checkpointer is not holding the writer lock,
48862 ** 1) The current writer (BtShared.pWriter) concludes its transaction, OR
48868 ** This feature is included to help prevent writer-starvation.
49651 ** only be a single writer).
49779 ** transaction. If there currently exists a writer, and p is not
49780 ** that writer, then the number of locks held by connections other
49781 ** than the writer must be about to drop to zero. In this case
49784 ** If there is not currently a writer, then BTS_PENDING must
61719 /* If the auto-commit flag is set and this is the only active writer
