Thomas, I hate to keep coming back to this... But I have built the most recent version 1.4.188 and I have been doing more testing in regards to the continual growth of the database due to the temporary LOB references.
In my case, my database file seems to continue to grow even with your new LOB_TIMEOUT value; I am continuing to issue the following statements every 10 minutes when the database file exceeds 50MB SET EXCLUSIVE 1 SET RETENTION_TIME 0 CHECKPOINT_SYNC SET RETENTION_TIME 45000 SET EXCLUSIVE 0 COMMIT However it rarely helps to reduce the db size. In my most recent test the database file had reached 500MB. After 30+ minutes of no db activity ( just active connections and the pseudo compact code from above / 10 mins. ) the db size did not change. After closing the database connections ( and ultimately the database itself )... it took about a minute for the database to completely close and remove the lock file and then the file size reduced 300MB. When I restarted the database and performed the pseudo compact code above it shrunk to 300K. This behavior does not seem to correlate well with your comments in this thread and what I would have expected. It still seems like a complete shutdown is required to reduce the file size. At the risk of beating this subject to death - do you have any thoughts on this? For the most part, It is the only issue and customer complaint that I get from my users concerning the H2 database implementation that I am using. -Kent On Tuesday, April 14, 2015 at 2:12:37 AM UTC-4, Thomas Mueller wrote: > > Hi, > > Yes, I added a timeout. > > First I wanted to keep the CLOB / BLOB objects only until the next > transaction. The problem is that some methods in JdbcConnection started a > new transaction (Statement.getQueryTimeout for example). It would be better > if those transactions are not required, but thats a change for another day. > > Regards, > Thomas > > > > On Sunday, April 12, 2015, Fred&Dani&Pandora&Aquiles <[email protected] > <javascript:>> wrote: > >> Hi, >> >> I think he added a timeout for BLOB and CLOB objects: >> >> References to BLOB and CLOB objects now have a timeout. The configuration >> setting is LOB_TIMEOUT (default 5 minutes). This should avoid growing the >> database file if there are many queries that return BLOB or CLOB objects, >> and the database is not closed for a longer time. >> >> Regards, >> >> Fred >> >> >> >> 2015-04-11 16:07 GMT-03:00 Kenton Garner <[email protected]>: >> >>> Thomas, what did you decide to do for this? >>> >>> -- >>> You received this message because you are subscribed to the Google >>> Groups "H2 Database" group. >>> To unsubscribe from this group and stop receiving emails from it, send >>> an email to [email protected]. >>> To post to this group, send email to [email protected]. >>> Visit this group at http://groups.google.com/group/h2-database. >>> For more options, visit https://groups.google.com/d/optout. >>> >> >> -- >> You received this message because you are subscribed to the Google Groups >> "H2 Database" group. >> To unsubscribe from this group and stop receiving emails from it, send an >> email to [email protected]. >> To post to this group, send email to [email protected]. >> Visit this group at http://groups.google.com/group/h2-database. >> For more options, visit https://groups.google.com/d/optout. >> > -- You received this message because you are subscribed to the Google Groups "H2 Database" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/h2-database. For more options, visit https://groups.google.com/d/optout.
