Hi Thomas, I wanted to follow up your post about Durability problems: http://www.h2database.com/html/advanced.html?highlight=fsync&search=fsync#durability_problems
If you follow the Mac OS X link you refer to you will find out the following: 1. fsync() flushes the OS-level disk cache to the disk, but does not force the disk to flush its on-board write cache. 2. Under Mac OS X you can use F_FULLFSYNC to force the disk to flush its on-board write cache. Source: http://lists.apple.com/archives/darwin-dev/2005/Feb/msg00072.html 3. Under Windows you can use FlushFileBuffers() to force the disk to flush its on-board write cache. Source: http://www.mail-archive.com/[email protected]/msg08132.html and http://old.nabble.com/Re%3A-Performance-problem-with-3.2.7-p1591614.html So first of all, we need to establish whether these sources are correct. If you rewrite your test in terms of FlushFileBuffers() does it flush to disk correctly? Next, assuming this works, we need to figure out whether this API is accessible through Java. If not, we can file a RFE with Oracle as well as looking into using JNI under H2 (ugly, but doable). What do you think? Gili -- You received this message because you are subscribed to the Google Groups "H2 Database" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/h2-database?hl=en.
