Hi, > INFORMATION_SCHEMA.lobs table grows rapidly
Yes. This is a problem for both MVStore and PageStore. The problem is that CLOB and BLOB objects must still be available even after the transaction is complete, and I think even after the result set is closed. And even after the row is removed. In previous versions of H2, BLOB and CLOB objects were removed too early; now they are removed when the database is closed. This will fix the "LOB is removed" problem, but results in a growing LOB table, which contains references (table -3 is temporary lobs). This is a problem, and I don't have a good solution for that I'm afraid. Closing the database or closing the connection from time to time are not good solutions I think. Maybe the temporary BLOB and CLOB objects should have a timeout (of let's say 1 minute by default)? Regards, Thomas On Sat, Mar 21, 2015 at 4:11 PM, Fred&Dani&Pandora&Aquiles < [email protected]> wrote: > Hi, > > >> But I disabled MVSTORE and MVCC by "MVSTORE=FALSE;MVCC=FALSE". Does the >> improvement help me? >> > > According to the changelog the improvement helps only with MV_STORE. In > this case, I think Thomas or Noel are more qualified to answer this > question. > > Regards, > > Fred > > -- > 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.
