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 at http://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.
