Home
last modified time | relevance | path

Searched refs:fsync (Results 1 – 12 of 12) sorted by relevance

/sqlite-3.40.0/test/
H A Dio.test33 # fsync() calls on the journal file).
37 # fsync() calls on the journal file, no need to set nRec
134 # The following INSERT updates 2 pages and requires 4 calls to fsync():
148 # only write 1 page and require a single fsync().
150 # The single fsync() is the database file. Only one page is reported as
156 # single fsync.
417 # have been no calls to fsync(). The file is probably about 30KB.
424 # The COMMIT requires a single fsync() - to the database file.
436 # than 4, calls to fsync(). The fsync() calls are on:
442 # Normally, when the SAFE_APPEND flag is not set, there is another fsync()
H A Dsync.test13 # This file implements tests to verify that fsync is disabled when
H A Dkvtest.c648 fsync(fileno(out)); in updateFile()
H A Dpermutations.test782 # the number of fsync() calls.
/sqlite-3.40.0/src/
H A Dtest_demovfs.c326 rc = fsync(p->fd); in demoSync()
479 rc = fsync(dfd); in demoDelete()
H A Dos_unix.c3563 # define fdatasync fsync
3653 if( rc ) rc = fsync(fd); in full_fsync()
3659 rc = fsync(fd); in full_fsync()
3664 rc = fsync(fd); in full_fsync()
H A Dtest_quota.c1087 rc = fsync(fileno(p->f)); in sqlite3_quota_fflush()
H A Dsqlite.h.in695 ** equal SQLITE_SYNC_NORMAL, that means to use normal fsync() semantics.
697 ** to use Mac OS X style fullsync instead of fsync().
748 ** [SQLITE_SYNC_FULL]. The first choice is the normal fsync().
H A Dshell.c.in4354 " --async Write to FILE without journal and fsync()",
/sqlite-3.40.0/ext/lsm1/lsm-test/
H A Dlsmtest.h37 # define fsync(fd) FlushFileBuffers((HANDLE)_get_osfhandle((fd))) macro
H A Dlsmtest_main.c1240 fsync(fd); in do_writer_test()
/sqlite-3.40.0/ext/lsm1/
H A Dlsm_unix.c46 # define fdatasync(x) fsync(x)