Hello,
When reading the docs I don't get a clear understanding on what strategy
I could/should use to backup a heavily used database (with frequent
reads & writes).
I have one application (A) with multiple threads reading & writing to
the database. Application (A) handles write locking internally, giving
write access to only 1 thread at a time.
I have another application (B) which among other things is responsible
for backing up the database from time to time. Application (B) is
currently using the backup API, but sometimes it gets starved so it
never reach completion.
Is there some way to take a snapshot of a database regardless if there
comes new writes / transactions while doing the backup, and just write a
copy of that snapshot as it was into a new database file?
_______________________________________________
sqlite-users mailing list
sqlite-users@mailinglists.sqlite.org
http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users
