I had the same issue previously, however as Noel States, changing to MV_STORE has helped tons. Noel and Thomas have done a lot of work in this area for MV_STORE to improve the database size after deleting the LOBs.
On Tuesday, February 23, 2016 at 1:16:40 PM UTC-5, Stephen Hendrix wrote: > > I'm using H2 JAR 1.4.191. Database URL is jdbc:h2:file:<file path> > ;DB_CLOSE_ON_EXIT=FALSE;MV_STORE=false;LOCK_TIMEOUT=10000;MVCC=true > > The database has a table with two columns: ID (BIGINT) and DATA (CLOB). I > wrote a script to repeatedly add and delete rows from that table. After > leaving it running for awhile, the database size grew to ~450MB. Eventually > it shrunk to about ~413MB, and it won't seem to compact smaller. The > database is practically empty except with a handful of entries in other > tables and 1 row in that LOB table. > > Running the Recover tool yielded the following stats: > > ---- Statistics ---- > -- page count: 101030, free: 0 > -- page data bytes: head 17407521, empty 187330865, rows 36487342 (23% > full) > -- data leaf 58%, 58893 page(s) > -- data node 0%, 222 page(s) > -- data overflow 0%, 24 page(s) > -- btree leaf 40%, 41258 page(s) > -- btree node 0%, 303 page(s) > -- free list 0%, 4 page(s) > -- stream data 0%, 323 page(s) > > Why is the space not getting reclaimed? > -- 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 https://groups.google.com/group/h2-database. For more options, visit https://groups.google.com/d/optout.
