contrib/sqlite3/sqlite3.c

1863   int (*xShmLock)(sqlite3_file*, int offset, int n, int flags);
2158 ** obtain a file lock using the xLock or xShmLock methods of the VFS.
2497 ** CAPI3REF: Flags for the xShmLock VFS method
2500 ** allowed by the xShmLock method of [sqlite3_io_methods].  The
2502 ** xShmLock method:
2514 ** The xShmLock method can transition between unlocked and SHARED or
2524 ** CAPI3REF: Maximum xShmLock index
2526 ** The xShmLock method on [sqlite3_io_methods] may use values
23413   return id->pMethods->xShmLock(id, offset, n, flags);
38717 ** different here than in posix.  In xShmLock(), one can go from unlocked
39198    unixShmLock,                /* xShmLock */                                \
46710   winShmLock,                     /* xShmLock */
46736   winShmLock,                     /* xShmLock */
48381   0,                               /* xShmLock */
63760   ** happen if the connection is actually in exclusive mode (as no xShmLock
98270   0,                /* xShmLock */
201999   **   * Calls to xShmLock(UNLOCK) to release the exclusive shm WRITER,
203371 **     avoid creating a *-shm file on disk. Additionally, xShmLock() calls
203374 **     xShmLock() is called before xShmMap().
203386 **     xShmLock() WRITER, CHECKPOINTER and READ0 locks on the target
203387 **     database file are recorded. xShmLock() calls to unlock the same
203396     int (*xShmLock)(sqlite3_file*,int,int,int) = p->pReal->pMethods->xShmLock;
203400         xShmLock(p->pReal, i, 1, SQLITE_SHM_UNLOCK|SQLITE_SHM_EXCLUSIVE);
203835       rc = p->pReal->pMethods->xShmLock(p->pReal, ofst, n, flags);
203955     rbuVfsShmLock,                /* xShmLock */