How do you know which items in the transaction log were not committed ?
On Apr 11, 3:36 pm, Thomas Mueller <[email protected]> wrote: > Hi, > > Could you use the Recover tool to find out which session (= > connection) was not committed? See at the beginning of the section > "---- Transaction log ----", and look at those sessions that were not > committed. > > Regards, > Thomas > > > > > > > > On Mon, Apr 9, 2012 at 11:28 AM, Carl Hasselskog <[email protected]> wrote: > > In my application the opening of the first connection is quite slow (often > >>60s). After profiling it I think it the result of a large undo-log (i.e. > > stage RECOVERY_STAGE_UNDO in recover()). The strange thing is that I am not > > creating any large transactions (only use auto-commit = true). What is it > > that can cause the undo-log to grow so much if you're not creating any > > transaction yourself? One theory I have is that I have some quite large > > ResultSets that create temporary tables and that are not closed very often. > > They are usually still open when the application is closed. Can that cause > > the transaction-log to grow? If so, do you have any tips on how I can work > > around it? > > > Thanks! > > Carl Hasselskog > > > -- > > 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/-/qI3CjiX4ebsJ. > > 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. -- 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.
