However, if the last connection does not shutdown cleanly, the WAL file will remain in the filesystem for recovery purposes. The write-ahead log or WAL file is used as a rollback journal and created when the first connection to the database is opened and is normally removed when the last connection to the database closes.
AUTOMATIC SSH RAM DISK CREATION AND LOADING UPDATE
home/pi/domoticz/domoticz.db-shm !! due to an update of the internal sqlite version home/pi/domoticz/domoticz.db-wal !! This will no longer work for domoticz version V4.11753 and newer If the hot journal files are moved, deleted, or renamed after a crash or power failure, then automatic recovery will not work and the database may go corrupt. SQLite must see the journal files in order to recover from a crash or power failure. The journal files have the same name as the original database file with the addition of -journal or -wal suffix.
Such journal files are described as "hot". However, while performing a transaction, information necessary to recover the database following a crash or power failure is stored in auxiliary journal files. SQLite normally stores all content in a single disk file. Please be aware of the following risk involved in moving the Write Ahead Log file to RAM. With respect to Domoticz, besides the log file, there are two files that can be moved to the RAM drive: With respect to the size of the RAM drive, 20MB is used as a standard trade off considering the usual size of the domoticz and openzwave temporary files, but this may have to be adjusted up or down based on the particular setup. This article will focus on the domoticz log and some temporary files as well as the openzwave log, that we will have reside in a RAM drive mounted as a new directory /tmp/log. Move most frequently written files to a ram drive to reduce SD Card wear.
0 kommentar(er)
