Thanks for the update. Is there a way to tell (based on trace) that there is a transaction in the state that prevents the the playing of the transaction log or that a transaction was rolled back based on the LOG_SIZE_LIMIT ? If I have said transaction I'd like to find it somehow and clean it up.
On Apr 19, 12:09 pm, Thomas Mueller <[email protected]> wrote: > Hi, > > Could someone explain the difference between MAX_LOG_SIZE and > > > LOG_SIZE_LIMIT and when you would use one over the other or should we > > use both. One talks about streams and one talks about sessions. What > > are the risks involved with setting either value to low? > > See the documentation > athttp://h2database.com/html/grammar.html#set_max_log_size > SET MAX_LOG_SIZE will not force transactions to be rolled back. If there is > an option transaction, the transaction log will continue to grow (without > bounds - until the oldest transaction is committed, out of disk space, or > the database is closed). > > But LOG_SIZE_LIMIT will force transactions to be rolled back. > > I will document this. > > Regards, > Thomas -- 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.
