We're experiencing a related problem: When we create a zip file using the BACKUP TO <filename> statement it appears that unzipping the database and opening it the first time takes quite a while (11 seconds), is there some kind of dirty-flag in the database so H2 executes some recovery procedure?
Morgan, which method do you use to create the backup? On 15 feb, 12:54, Morgan Grignard <[email protected]> wrote: > Hi, > > We're facing a trouble in a specific use case : > We try to create a backup (zipfile) justafterclosingaconnection > to adatabase. > We experiment some data corruption in this case and we're forcing to > add a wait lock before tozipfile, in order to wait H2's work to be > finished. > > Is there a way to know when H2 has really finished his job or to > configure aconnectionwhich wait on close. -- 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.
