On Fri, Apr 11, 2008 at 09:08:04AM -0700, Ken scratched on the wall: > Even with Synchronous = off > > Sqlite will flush its buffers upon the commit!
I'm not talking about SQLite's buffers, I'm talking about the file-system driver of the operating system. > As a "close" system call is performed! That still doesn't mean the pages are actually written to disk by the operating system, just that they're going to be marked as no longer in use and queued for writing. Nowhere in the POSIX spec for close() does it say the file needs to be sync'ed (especially in a blocking fashion) when close() is called. -j > "Jay A. Kreibich" <[EMAIL PROTECTED]> wrote: On Fri, Apr 11, 2008 at > 03:28:47PM +0200, Martin Engelschalk scratched on the wall: > > Hello Donald, > > > > I don't think so: The journal files are not synchronized on SYNCHRONOUS > > = OFF, but they are still written, so transactions are still possible. > > Yes, but if I understand the SYNCHRONOUS=OFF setting correctly, there > is no reason the believe the journal files will ever make it out of the > operating system's file cache. Even if the OS does decide to spool > them off to disk, that's going to happen in an async manner. -- Jay A. Kreibich < J A Y @ K R E I B I.C H > "'People who live in bamboo houses should not throw pandas.' Jesus said that." - "The Ninja", www.AskANinja.com, "Special Delivery 10: Pop!Tech 2006" _______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
