For performance reasons, our client was doing the following for a large insert: a constraint was being removed, insert the data, then constraint added again.
On recovery, these steps were being repeated many times when replaying the transaction log. The startup was taking over 11 minutes on a small CPU. We are changing the client to not need the constraint and therefore not add and remove it. Now, the recovery time is much better. But, I'm still looking at ways (h2 options or best practices) to keep the recovery time as low as possible after power failure. On Monday, April 23, 2012 3:09:51 AM UTC-4, Thomas Mueller wrote: > > Hi, > > After power failure, the first connection takes quite some time. > > > How much time does it take exactly? > > >> Looking at the trace, it looks like indexes are being rebuilt (with some >> indexes rebuilt multiple times). > > > Yes, it looks like an index is re-built. Why do you think some indexes are > rebuilt multiple times? > > >> What settings can be used to reduce the amount of time to recover after >> reboot (smaller transaction log, etc)? >> > > I wonder if there were large, open transactions at the time of the power > failure. Do you have a reproducible test case? > > Regards, > Thomas > > -- You received this message because you are subscribed to the Google Groups "H2 Database" group. To view this discussion on the web visit https://groups.google.com/d/msg/h2-database/-/BHXWpJMVvrIJ. 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.
