On 5/3/19, Jens Alfke <j...@mooseyard.com> wrote: > > Thanks, Simon. So the rekey is expected to double the database file size?
Database size should be the same before and after rekey. The rekey operation will generate journal file entries that are about the same size as the original database (actually slightly larger due to extra per-page header information stored in the journal) but that temporary space is transient. It is only used in the event of a system crash occurs in the middle of a rekey. Once the operation completes, total disk usage reverts to what it was before. No VACUUM required. VACUUM is *highly* recommended for security if you take an unencrypted database that has never before been encrypted and "rekey" it into an encrypted database. That is a totally separate issue. -- D. Richard Hipp d...@sqlite.org _______________________________________________ sqlite-users mailing list sqlite-users@mailinglists.sqlite.org http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users
