>That is exactly it. We delete the LOBs on session close and/or after a
configurable timeout.<
>
>
>
>From my testcase's point of view, neither is happening. Regardless of
LOB_TIMEOUT set and repeated DB reopens, DB files grow in size as LOBs are
read.
I understand that technically you might be correct and the reason you
mentioned ("We just don't seem to be doing a very good job of compacting
here, resulting in a file with tons of partially filled (1%) chunks") might
be the real culprit, but from the user standpoint it doesn't matter.
Fortunately MVStore/BINARY works like a charm.
--
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.
