Lines Matching refs:blocking
3 On some Unix-like systems, SQLite may be configured to use POSIX blocking locks
10 need to continuously poll the database lock, and (b) using blocking locks
14 Only read/write clients use blocking locks. Clients that have read-only access
15 to the \*-shm file nevery use blocking locks.
18 a result of blocking database locks. But it is of course possible for threads
29 Without blocking locks, if two clients attempt recovery simultaneously, one
31 returns SQLITE\_BUSY to the user. With blocking locks configured, the second
37 have no need of blocking locks.
42 blocking lock is used to obtain the CHECKPOINTER lock in this case. A snapshot
48 A database writer must obtain the exclusive WRITER lock. It uses a blocking
58 to a write-transaction. In that case a non-blocking lock is used.
71 All of the above use blocking locks.
75 With blocking locks configured, the only cases in which clients should see an
78 * if the OS does not grant a blocking lock before the configured timeout
82 In all other cases the blocking locks implementation should prevent clients