Hi,
I found a strange behavior of the sqlite 3.7.2 with WAL journal mode.
Yesterday I found my application DB with a -wal file of 1,5GB and a -shm
file of few MB (about 9MB) with a DB file of 1,2GB: in this
situation I got the process memory wasted by "mapped file" of the -shm
file. It seams that the file is mapped a lot of times in memory so the
process memory become 2GB and it can't allocate more memory. In that
situation operation made on the DB cause I/O disk errors probably due to
the wasted memory.
I'm doing some other test to reproduce the problem, but I think that
could be when I got a lot of operation between a BEGIN; COMMIT;
So is it ok to use the BEGIN; COMMIT; with the WAL journal activated?
is there some kind of limit in the number of operation between a BEGIN;
COMMIT; statement?
I try to use the PRAGMA wal_checkpoint; to try resolve this situation,
but seams that command was ignored by sqlite because the -wal file does
not change in size, even the DB file.
_______________________________________________
sqlite-users mailing list
sqlite-users@sqlite.org
http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
