-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 rschnitzer wrote: > So my original question still stands about the side effects of > integrity_check and whether it would interfere with the continuous 24/7, > multiple-times-per-second access by our mission critical application.
You would need to measure this (CPU vs I/O tradeoff) but you may instead want to use the SQLite backup API to make a copy of the database and then run the integrity check on that copy. At that point you won't care about how long the integrity check takes, and as a bonus you have a backup of the database. Roger -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iEYEARECAAYFAkqwMj8ACgkQmOOfHg372QSmYQCgkOTGuSVzNZV0j1hQtyRGdJhN Ke8An10QX0ty1fEQkxjPEV4uAyYsqUhs =KRyP -----END PGP SIGNATURE----- _______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
