At Chromium shutdown, various services desire to write data to their SQLite databases, which results in a (small) thundering herd of fsyncs, which makes shutdown slower than it could be. Normally, one could enable WAL mode to amortize the fsync cost across longer periods than a single transaction, but as best I can tell, sqlite3_close() requires the WAL checkpoint, so won't help.
Is there any clean way to request no WAL checkpoint on sqlite3_close()? An obvious solution would be to simply not call sqlite3_close(), though that has various other unfortunate side effects. Thanks, scott _______________________________________________ sqlite-users mailing list sqlite-users@mailinglists.sqlite.org http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users
