Hi, Please consider the attached testcase. The WAL file should grow to at most 1 MB. This limit is exceeded, because the script adds data while a second cursor has an active SELECT query. However, when the SELECT query finishes, the WAL file is not auto-checkpointed either.
An access pattern similar to the one in the testcase thus results in unbounded growth of the WAL file, even though auto-checkpointing is enabled, and there are time slots where it could be performed (no transaction active). $ python bug_or_not.py test.sqlite Max WAL file should be 1 MB Starting query with cursor 2.. Inserting 5 MB of data with cursor 1 Size of WAL file is now: 16467.0 kB Finishing cursor 2 query.. Size of WAL file is now: 16467.0 kB Starting query with cursor 2.. Inserting 5 MB of data with cursor 1 Size of WAL file is now: 32954.0 kB Finishing cursor 2 query.. Size of WAL file is now: 32954.0 kB Bug or not? Best, -Nikolaus -- »Time flies like an arrow, fruit flies like a Banana.« PGP fingerprint: 5B93 61F8 4EA2 E279 ABF6 02CF A9AD B7F8 AE4E 425C
_______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
