Does this also affect FOSSIL, or is auto vacuum never used there?
-----Original Message-----
From: D. Richard Hipp
Sent: Thursday, June 08, 2017 6:57 PM
To: sqlite-annou...@mailinglists.sqlite.org ;
sqlite-users@mailinglists.sqlite.org
Subject: [sqlite] Version 3.19.3 containing an important bug fix
A bug in the auto_vacuum logic for SQLite versions 3.16.0 through 3.19.2 can
(rarely) lead to database corruption. SQLite version 3.19.3 has just been
released to fix this bug.
https://sqlite.org/
https://sqlite.org/download.html
See https://www.sqlite.org/src/info/fda22108 for more information about the
bug. The problem can only arise on databases that have auto_vacuum enabled.
Nevertheless, all users are encouraged to update. If you have database
files that are in auto_vacuum mode, you should consider running VACUUM on
those databases after updating, in order to clear any database
inconsistencies that might have been introduced by this bug.
If you encounter any problems with this release, please send email to
sqlite-users@mailinglists.sqlite.org or directly to me. Thanks.
--
D. Richard Hipp
d...@sqlite.org
_______________________________________________
sqlite-users mailing list
sqlite-users@mailinglists.sqlite.org
http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users
_______________________________________________
sqlite-users mailing list
sqlite-users@mailinglists.sqlite.org
http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users
