transactions - Clarification regarding journal_size_limit in SQLite -


if set journal_size_limit = 67110000 (64 mib) able to:

  1. work / commit transactions on value (somewhat unlikely)
  2. be able perform vacuum (even if database has 3 gib or more)

the vacuum command works copying contents of database temporary database file , overwriting original contents of temporary file. when overwriting original, rollback journal or write-ahead log wal file used other database transaction. means when vacuuming database, as twice size of original database file required in free disk space.

it's not entirely clear in documentation, , appreciate if tell me sure.

the journal_size_limit not upper limit on transaction journal; upper limit inactive transaction journal.

after transaction has finished, journal not needed, not deleting journal can make things faster because file system not need free data , reallocate next transaction.

the purpose of setting limit size of unused journal data.


Comments

Popular posts from this blog

jquery - How can I dynamically add a browser tab? -

node.js - Getting the socket id,user id pair of a logged in user(s) -

keyboard - C++ GetAsyncKeyState alternative -