If you want to downgrade, you will need to do a dump and restore
--
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 h2-database+unsubscr...@googlegroups.com.
To
I can't by any means use an unscalable format because I want to provide a
long-term working environment without being anxious it will fail sometimes
I just want to clean the database, bring it to minimal size, and downgrade to
1.3 stable
Can anyone help me please? I have been waiting for very
Sadly, the 'SHUTDOWN DEFRAG' just closes the connection pool, but the file size
does not change at all. (Tried with h2 driver 1.4.185 and latest 192)
The version I was using normally is:
h2: 1.4.185
And before I was on 1.3
Do you think I could roll back to latest stable setting the version to
Hi,
The PageStore is a classical storage system with redo and undo log, and
overwrites old data (in a save way). The MVStore doesn't overwrite data
immediately, but wait doing that for at least 1 minute. In theory, the
PageStore needs less (measurable) disk space, but in practise, with solid
Hi,
Thanks for your attention.
Sadly, the 'SHUTDOWN DEFRAG' just closes the connection pool, but the file
size does not change at all. (Tried with h2 driver 1.4.185 and latest 192)
The version I was using normally is:
h2: 1.4.185
Do you think I could roll back to latest stable setting the
Hi,
With the MVStore storage engine, which is the default in version 1.4.x, the
file size is typically a few times larger than the "real data". This is
expected. If you run "shutdown defrag", the file size should decrease. Does
it do that?
Reason for the larger file size: to speed up writes
This is my first post on this group,
Hello to everyone! :)
I have a problem with my H2 DATABASE.
I am seriously worried by the size it is getting, it is now about 350mb
(Yeah I know it's not the largest one), but my worries go all to the future
and how it will scale in the long run.
Issues:
-
