Hi,
Is this a new change? I have an app using multi-threaded mode and the
backup does not block other queries. Does it mean if the backup is
synchronised on the database and the queries are synchronised on the
session then the backup does not block queries?
Or was it found dangerous that the backup not blocking could cause a
corrupted backup (Because of blocks being changed while the backup is
copying?) ?
Thanks, Ryan
The documentation is incorrect no longer correct. The BACKUP statement
is synchronized on the database, even when using the multi-threaded
mode. I will change the documentation. I will also add a feature
request "The BACKUP statement should not synchronize on the database,
and therefore should not block other users."
I will also change the documentation: "The resulting backup is
transactionally consistent, meaning the consistency and atomicy rules
apply."
--
You received this message because you are subscribed to the Google Groups "H2
Database" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit this group at
http://groups.google.com/group/h2-database?hl=en.
