On 8/15/15, Ashwin Hirschi <sqlite-l at reflexis.com> wrote: > > Hello, > > I've recently found SQLite doesn't always remove its journal files anymore. > > The issue seems to occur when opening WAL databases in read-only mode > (i.e. using SQLITE_OPEN_READONLY). > > A scenario to reproduce this (using version 3.8.11.1) looks like: > > 1. open a WAL database in read-only mode > 2. prepare & finalize a query > 3. close the database > > The "-shm" and "-wal" journal files are created during the prepare() in > step 2. But, after step 3, they're both still present.
I am not able to reproduce the observed behavior on either Ubuntu, Win7, or Win8. Please provide additional clues. > > If the database is opened in read-write mode, everything is fine. Lastly, > I'm having the issue on a Windows 10 machine and am not currently able to > test anywhere else... > > So, can anyone else reproduce the above scenario? > > Ashwin. > > P.S. I've also checked some older SQLite versions. It looks like this > unfortunate "non-cleanup" was introduced in 3.8.11. > _______________________________________________ > sqlite-users mailing list > sqlite-users at mailinglists.sqlite.org > http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users > -- D. Richard Hipp drh at sqlite.org
