Hi guys, I haven't been able to figure this one out from the docs, nor have I stumbled onto the right section of the source.
Say you have two separate processes accessing an sqlite DB. P1 starts a transaction, reads page #5, ends transaction. P2 starts a transaction, modifies page #5, ends transaction. P1 starts a new transaction and reads page #5 again. At this point P1 still has page #5 cached in memory, but clearly it needs to read from disk to pick up the changes. How does sqlite determine that the cached page is out of date? Ultimately the question I'm trying to answer is whether increasing the size of the pager cache will reduce the amount of I/O required by a single process in the case where a database is modified concurrently. Cheers, -Rowan _______________________________________________ sqlite-users mailing list sqlite-users@mailinglists.sqlite.org http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users
