I see, then what I'm seeing is just normal behavior of the writes being flushed to disk. I read what I wanted to hear about synchronous=NORMAL delaying writes to the -wal file. Instead I'm going to see if I can move -wal to a ramdisk and see how that will affect db integrity with power losses at in-opportune times.
Thank you. On Fri, 2017-12-29 at 11:17 -0500, Richard Hipp wrote: > On 12/28/17, Ian Freeman <i...@ifreeman.net> wrote: > > I have configured journal_mode=WAL, synchronous=NORMAL, and > > disabled > > autocheckpointing, and yet the -wal file is modified after every > > update > > operation... > > That is correct. "sync" means forcing the data from the internal > operating-system buffers out to persistent storage on your disk > drive, > where it will survive and OS reset or power loss. The WAL is written > on every transaction, in the sense that the content is moved into the > operating system. But it is only synced to persistent storage on a > checkpoint. > _______________________________________________ sqlite-users mailing list sqlite-users@mailinglists.sqlite.org http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users
