Hick Gunter wrote > If you are running an SQLite version 3.11.0 or newer, only pages that are > changed for the first time in the transaction are copied to the WAL file, > thus extending it. > > While progressing the transaction, the rate of "newly changed" to "changed > again" pages will shift towards re-reading and rewriting the WAL file copy > of a page; this will tend to slow down the rate at which the WAL file is > growing, even at a constant delete rate, until every page has been updated > at least once, and then stop growing until all the remaining deletes have > been processed.
Running 3.19; thanks for the explanation, this never occured to me and makes perfect sense. -- Sent from: http://sqlite.1065341.n5.nabble.com/ _______________________________________________ sqlite-users mailing list sqlite-users@mailinglists.sqlite.org http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users
