Does write blocking still come into play when using "vaccum into", or are writes put into the WAL file? I know that with the regular backup API, any writes to the DB restarts the backup process, but I hadn't thought about putting either into a transaction. (I'm an I-D-TEN-T, I know)
On Wed, Feb 27, 2019 at 10:20 AM Richard Hipp <d...@sqlite.org> wrote: > > I assume you are using WAL mode? If not, you should be. Just making > that one change might solve your problem. > > In WAL mode, run the entire backup inside a transaction. Or use the > new VACUUM INTO feature to make your backup. > > -- > 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 > _______________________________________________ sqlite-users mailing list sqlite-users@mailinglists.sqlite.org http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users
