3 ms·
> "No, the issue is it doesn't have high availability features: failover, snapshots, concurrent backups, etc." I think it has concurrent backups via the backup
by hexmiles 6y ago
> "No, the issue is it doesn't have high availability features: failover, snapshots, concurrent backups, etc."
I think it has concurrent backups via the backup api:
https://www.sqlite.org/backup.html https://www.sqlite.org/backup.html
- formerly_proven 6y agoI'd expect this to be unnecessary in WAL mode (which you should use, when possible), since WAL allows concurrent readers while permitting up to one writer. In the old undo-log mode (which remains the default for compatibility) writing excluded readers.
- nayuki 6y agoI don't think you can do naive file copy backups even in WAL mode. WAL will checkpoint the log into the main database file from time to time. You need to use the SQLite backup API to let you make a backup while blocking any potential checkpointing.
- formerly_proven 6y agoSorry, I was unclear. I meant the "copy a few pages then sleep for some time to release the database lock" part. With WAL mode you should just be able to copy as fast as you can without disturbing other readers or the writer. SQLite also has a similar SQL built in, VACUUM INTO. That's nice because the backup API just copies all pages (iirc).