I didn't realise VACUUM could be so memory hungry but that should still be ok for us because:
My system is an embedded arm9 running an RTOS with a flash file system, so no disk. Database files will reside in a flash based r/w partition. The /var is currently mounted on a RAM disk, which should mean faster VACUUM cleaning than flash. We should have more than enough RAM for the VACUUM operation and it won't matter if the unit dies because of the rollback mechanism you and Dan mention. Thanks again, Scooby drh-2 wrote: > > scoobyjh <[EMAIL PROTECTED]> wrote: >> When VACUUM cleaning a database it creates a temporary file by default in >> /var/tmp. What happens when power is lost or unit crashes? Can the >> database >> be correupted or lose data? >> > > VACUUM generates a rollback journal. So losing power > in the middle of a VACUUM will just cause the database > to revert to its original state when power is restored. > > Note, however, that because of the temporary file and the > journal, VACUUM can use temporary disk space that is a > little more than twice the size of the original database > file. > > -- > D. Richard Hipp <[EMAIL PROTECTED]> > > > ----------------------------------------------------------------------------- > To unsubscribe, send email to [EMAIL PROTECTED] > ----------------------------------------------------------------------------- > > > -- View this message in context: http://www.nabble.com/Is-VACUUM-safe-from-power-loss-crashing-tf4136949.html#a11777692 Sent from the SQLite mailing list archive at Nabble.com. ----------------------------------------------------------------------------- To unsubscribe, send email to [EMAIL PROTECTED] -----------------------------------------------------------------------------
