Doing updates is going to create transaction log entries, so yes the DB
will grow.
If you want to eliminate that you can turn the transaction log off, but
then you risk corrupting your database.
On 2012-04-11 19:26, Bob wrote:
I have an database from a system that crashed due to lack of memory,
The database size is 45M. If I open the database and simply close it
in the h2 console it shrinks to 30M. This leads me to believe there
was 15M of temporary stuff the was cleaned up as part of the normal
compression on shutdown.
My concern is I only have 512M total of disk on my device, The
database should only be used for reads, though there may have been
some updates but no inserts or deletes. How do I figure out what that
extra 15M was used for and how can I stop it from growing?
I have version 1.3.160, I see in the change log that version 1.3.165
has a transaction log fix - would that help? Is there some way to know
whats in that 15M? I still have both versions....
So in general I need to keep the disk footprint as small as
possible... any suggestions?
Bob
--
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.
