I saw below thing listed as disadvantage in http://www.sqlite.org/wal.html#ckpt .
“WAL works best with smaller transactions. WAL does not work well for very large transactions. For transactions larger than about 100 megabytes, traditional rollback journal modes will likely be faster. For transactions in excess of a gigabyte, WAL mode may fail with an I/O or disk-full error. It is recommended that one of the rollback journal modes be used for transactions larger than a few dozen megabytes.” Query: ---------- I would like to understand if the WAL file size grows beyond 100 megabytes to range say 500 to 900 megabytes, what would be the impact ?. - Is it just a read/write performance impact ? Or - There will be disk failure or database would get corrupt ? We have decided to move our application running from TRUNCATE mode to WAL mode. To avoid WAL size growing larger, we are planning to have maintenance window, where application wont be doing any read/write to the database so check point can be run to reduce the WAL file size. As always appreciate experts valuable comments in making my application work well with sqlite database. Thank you -Veeresh _______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
