Hi, This is already on my list. The problem is: if you delete a lot of data and then close the database, the next time it is opened the database will overwrite the empty space with zeroes. This is not a problem for smaller databases, and it's not a problem unless you delete a lot of data. My plan is to change the behavior so that empty space is not overwritten, at least not when you open the database. But this change is relatively dangerous, I need to test it well. By the way it's not necessary for this to happen that you run DELETE or TRUNCATE or DROP. A lot of data is also deleted internally by copying tables (ALTER TABLE), or if you use large transactions. There are other cases as well.
As a workaround, I suggest to run SHUTDOWN COMPACT when you close the database. This will take some time, as it (potentially) moves a lot of data around. But after that, startup will be quick. I hope I will be able to solve this problem soon. > I generated this test data as a CSV How exactly did you import? Did you use CREATE TABLE ... AS SELECT ...? That should be the fastest way. Regards, Thomas -- 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.
