Hi, FYI: I will probably remove the (quite new) feature LOG_SIZE_LIMIT, because it doesn't always work correctly (for example, locks are released unexpectedly).
Regards, Thomas On Fri, Apr 13, 2012 at 3:01 PM, IntensiveH2 <[email protected]> wrote: > Hi, > > No, I speak about LOG_SIZE_LIMIT (about rolling backtransactions). > Also, by default why LOG_SIZE_LIMIT is not equal to MAX_LOG_SIZE. > > Thanks. > Le vendredi 13 avril 2012 14:53:51 UTC+2, Thomas Mueller a écrit : >> >> Hi, >> >> Probably you mean MAX_LOG_SIZE, there is a SQL statement for that: >> http://h2database.com/html/grammar.html#set_max_log_size >> >> LOG_SIZE_LIMIT is about something else, it's about rolling back >> transactions that were not committed since a long time. I guess I >> should rename this setting. >> >> 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/-/VdhBnit9z2YJ. > > 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.
