Hello Richard. > On Mon, Dec 15, 2014 at 11:11 AM, Paul <de...@ukr.net> wrote: > > > > Hello, dear developers > > > > Recently I've stumbled upon a very rare and strange bug. > > The result of this is abnormal memory usage, that does not allow us to > > remove > > fair number of rows from a table due to the limit of memory, available for > > 32bit > > process. This is strange, because database size is somewhat small: 79M. > > > > What happens if you omit the "PRAGMA temp_store=MEMORY" and "PRAGMA > journal_mode=MEMORY" and allow SQLite to store (necessary) recovery > information on disk? Does memory usage go down then? >
With " PRAGMA temp_store = MEMORY;" " PRAGMA journal_mode = DELETE;" Current mem: 0 Hi mem: 1294083360 * No disk activity With only temp_store on disk: " PRAGMA temp_store = FILE;" " PRAGMA journal_mode = MEMORY;" Current mem: 0 Hi mem: 1301739808 * No disk activity With " PRAGMA temp_store = FILE;" " PRAGMA journal_mode = DELETE;" Current mem: 0 Hi mem: 8012872 * A lot of data is written on disk. _______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
