Hi, I'm using SQLite in WAL mode in the following scenario: - One writer which continuously writes new rows and deletes older ones - Multiple readers performing queries
Writer and readers are running each in a separate process. The (Inactive) Journal Size limit is set to 100MB by pragmas and in normal usage this request seems to be honoured (i.e. the file does not grow bigger than that). I've however run into a situation where the .db-wal grows up to several Gigabytes, and the main .db file stays small. I believe this can be explained by some stale transaction in the system preventing the WAL pages from getting discarded (after being copied to the main database file). Any suggestion on how I can diagnose this situation, i.e. identify the offending process? Thank you, Gerlando _______________________________________________ sqlite-users mailing list sqlite-users@mailinglists.sqlite.org http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users
