A busy read transaction holds the WAL open and prevent is from being reset. If you find that your WAL is growing without bound, this suggests that you have an unfinalized query hanging around someplace, perhaps in a separate hung process.
2010/7/6 Alexey Pechnikov <pechni...@mobigroup.ru> > $ ls -lh > -rw-r--r-- 1 veter veter 700M Июл 7 00:55 test.db > -rw-r--r-- 1 veter veter 192K Июл 7 00:55 test.db-shm > -rw-r--r-- 1 veter veter 186M Июл 7 00:55 test.db-wal > -rwxr-xr-x 1 veter veter 3,0K Июл 7 00:47 test.tcl > $ sqlite3 test.db 'pragma page_size' > 8192 > $ sqlite3 test.db 'PRAGMA wal_autocheckpoint' > 1000 > > > -- > Best regards, Alexey Pechnikov. > http://pechnikov.tel/ > _______________________________________________ > 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
