Hello.

1. You use an old unsupported version with known issues, including issue 
with unreasonably large databases after execution of huge queries. Only 
issues with 1.4.199 are accepted. Note that there are some issues with 
automatic upgrade, it's safer to create a new database and populate it with 
SQL script that was exported by the old version.

2. MVStore is a copy-on-write storage that persist every transaction for at 
least 45 seconds by default. It can use more space than old PageStore 
engine.

3. Database file after migration can be not yet compacted depending on many 
factors and size difference can be caused by such situation. You can try to 
use SHUTDOWN COMPACT after import, it can help in some cases.

4. If you don't like the new storage engine and you don't need row-level 
locks and high concurrency you can continue to use the old PageStore engine 
in new versions of H2. Beware: with recent versions it's enough to add 
;MV_STORE=FALSE to database URL to create a new database with this engine, 
but in older versions, including 1.4.196, you need to add 
;MV_STORE=FALSE;MVCC=FALSE because PageStore can be corrupted if MVCC is 
enabled. New versions don't have the MVCC setting any more and use MVCC 
only with MVStore engine.

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/h2-database/72a203ae-848f-4535-a760-c09dfe86efca%40googlegroups.com.

Reply via email to