Lines Matching refs:fsync

1165 ** equal SQLITE_SYNC_NORMAL, that means to use normal fsync() semantics.
1167 ** to use Mac OS X style fullsync instead of fsync().
1218 ** [SQLITE_SYNC_FULL]. The first choice is the normal fsync().
10167 #define SQLITE_FullFSync 0x00002000 /* Use full fsync on the backend */
10168 #define SQLITE_CkptFullFSync 0x00004000 /* Use full fsync for checkpoint */
26444 ** fsync(). If you know that your system does support fdatasync() correctly,
26448 # define fdatasync fsync
26464 ** The fsync() system call does not work as advertised on many
26468 ** The SQLITE_NO_SYNC macro disables all fsync()s. This is useful
26480 ** and fsync(), Ted tells us, is that fdatasync() will not flush the
26505 /* Record the number of times that we do a normal fsync() and
26525 /* If the FULLFSYNC failed, fall back to attempting an fsync().
26528 ** isn't supported for this file system. So, attempt an fsync
26533 if( rc ) rc = fsync(fd);
26537 ** so currently we default to the macro that redefines fdatasync to fsync
26539 rc = fsync(fd);
26544 rc = fsync(fd);
26563 ** fsync() a directory to make sure file creation and deletion events
26604 ** has been created by fsync-ing the directory that contains the file.
26637 /* Also fsync the directory containing the file if the DIRSYNC flag
26639 ** are unable to fsync a directory, so ignore errors on the fsync.
28663 ** is called the directory file descriptor will be fsync()ed and close()d.
28882 ** Delete the file at zPath. If the dirSync argument is true, fsync()
28888 int dirSync /* If true, fsync() directory after deleting file */
28907 if( fsync(fd)==-1 )
28909 if( fsync(fd) )
28912 rc = unixLogError(SQLITE_IOERR_DIR_FSYNC, "fsync", zPath);
29876 fsync(conchFile->h);
41770 ** SQLITE_SYNC_FULL macro means to use the MacOSX-style full-fsync
41772 ** ordinary fsync() call. There is no difference between SQLITE_SYNC_FULL
44896 ** Return true if fsync() calls are disabled for this pager. Return FALSE
44897 ** if fsync()s are executed normally.
47133 ** process, foreground threads will never block on a lengthy fsync call.
47140 ** WAL content is copied into the database file. This second fsync makes
48142 ** the next fsync should occur - passed from sqlite3WalFrames() into
48149 int syncFlags; /* Flags for the fsync */
51673 ** operate asynchronously - it will not stop to do fsync()s