I am experiencing a very strange behaviour of H2 1.4.197 in embedded mode. I have an MVStore database that is created by dumping an existing database to SQL and then executing that SQL on a newly created database. I repeat this process to copy DB1 => DB2, DB2 => DB3, etc.
Each time the last created database is ~300Mb in size. But once I perform an additional copy on the new database it grows to ~3Gb while the newly created copy again is ~300Mb. This behaviour is consistent. When I only dump the database to a plain SQL script and do not create a new copy it still blows up to ~3Gb. No writes are done to the database that is dumped but it is opened in read/write mode. Dumps are done by executing the command "SCRIPT" as a PreparedStatement and reading the returned SQL statements from the ResultSet. Is there any explanation for this behaviour and can it be prevented? Kind regards, Silvio Bierman -- 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.
