I made one additional observation which is quite puzzling. The increase in database size happens asynchronously. At the moment the SQL script has been written (and the connection that was used to issue the "SCRIPT" command has been closed) the database is only partially inflated. Some background thread is working hard on that though, since it takes only 15 seconds to get to the inflation factor of ~10.
This issue really concerns me. I have servers where the size of a PageStore database approaches 50% of the total disk size (I used to go up to 95% with PostgreSQL databases). This has worked flawlessly for years now and no strange and unexpected increments in database size have ever happened there. After positive initial results from tests with some (smaller) databases converted from PageStore to MVStore I was considering taking MVStore into production. But unless a hard upper limit on the transient inflation factor can be guaranteed production use is not an option. I would really appreciate if one of the developers could shed a light on this. -- 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.
