Message70842
Python currently provides os.fsync to call the POSIX 'fsync' on
platforms that support it. While this function forces the operating
system to force a file buffer to the storage device, data may still be
waiting in the hardware write buffers on the storage device. Certain
platforms (so far, only OS X) provide "fullfsync" [1] to request that
storage devices flush their write buffers to the actual physical media.
This functionality is especially useful to VCS and DB developers, and
already appears in SQLite [2] and MySQL [3], amongst others.
This patch includes code changes to Modules/posixmodule.c that exposes
os.fullfsync on supported platforms, including the appropriate
documentation added to Doc/library/os.rst
-Ian Charnas
[1] Discussion of fsync and fullfsync on darwin platform:
http://lists.apple.com/archives/darwin-dev/2005/Feb/msg00072.html
[2] SQLite uses fullfsync on all platforms that define it:
http://www.sqlite.org/cvstrac/fileview?f=sqlite/src/os_unix.c
[3] MySQL uses fullfsync only on the darwin platform and only when
F_FULLFSYNC is defined as 51, which seems to be short-sighted in that
this symbol may change value in future versions of OS X. To see this
code, download a mysql 5.x source snapshot and open up
mysql-<version-number>/innobase/os/os0file.c |
|
Date |
User |
Action |
Args |
2008-08-07 17:31:59 | icharnas | set | recipients:
+ icharnas |
2008-08-07 17:31:59 | icharnas | set | messageid: <1218130319.91.0.361112026251.issue3517@psf.upfronthosting.co.za> |
2008-08-07 17:31:58 | icharnas | link | issue3517 messages |
2008-08-07 17:31:57 | icharnas | create | |
|