Tracking bug for infrastructure changes to enable SQLite WAL mode. |
|||
Issue descriptionBackground: issue 78507 and https://www.sqlite.org/wal.html This bug is about tracking changes to third_party/sqlite/ and sql/ to allow other code to make use of WAL mode. For instance: - change SQLite checkpoint-on-close defaults. - sql::Connection API changes. - sql::Connection implementation changes. - sql::Recovery support. - sql::test:: support. Basically, infrastructure changes without changes to how Chromium operates in production.
,
Apr 19 2017
The following revision refers to this bug: https://chromium.googlesource.com/chromium/src.git/+/f7fcc45c7cfb05f8fed045d38153792baba57e89 commit f7fcc45c7cfb05f8fed045d38153792baba57e89 Author: shess <shess@chromium.org> Date: Wed Apr 19 22:10:41 2017 [sql] Verify control of close-time WAL checkpoint. SQLite WAL mode by default checkpoints the WAL to the main database at close time. Chromium closes databases at shutdown, which causes shutdown slowdowns due to buffered data being flushed. WAL checkpointing would effectively increase the amount of buffered data being flushed. [WAL mode is currently not in use by Chromium.] BUG=675264 Review-Url: https://codereview.chromium.org/2827673006 Cr-Commit-Position: refs/heads/master@{#465772} [modify] https://crrev.com/f7fcc45c7cfb05f8fed045d38153792baba57e89/sql/connection.h [modify] https://crrev.com/f7fcc45c7cfb05f8fed045d38153792baba57e89/sql/sqlite_features_unittest.cc
,
Jun 21 2017
,
Sep 21 2017
|
|||
►
Sign in to add a comment |
|||
Comment 1 by sh...@chromium.org
, Apr 18 2017