On Mon, Feb 25, 2013 at 8:46 AM, Joost Voogt <joostvo...@gmail.com> wrote:
> Apparently I did something wrong the first time when I tried the exclusive > lock because now I don't see SQLite reading the file change counter > anymore. Sorry for that. > > I did some performance measurement on an FTS index on Android and I see > some performance gain of around 5%. That is a nice gain but I'm wondering > if there are any big drawbacks of using the exclusive lock. Probably when > the FTS process (app) crashes you'll have to reboot the device as there > still is an exclusive lock on the database? Are there any other problems > that I'm unaware of which using the exclusive lock has? > No. The lock is an ordinary Posix Advisory Lock and automatically goes away when the application crashes. The only disadvantage to an exclusive lock is that other processes can neither read nor write to the database file while you are holding it. > _______________________________________________ > sqlite-users mailing list > sqlite-users@sqlite.org > http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users > -- D. Richard Hipp d...@sqlite.org _______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
