I got the same result as yours. SHUTDOWN COMPACT didn't compact the database. I am testing against a 1.1GB database. I tried SHUTDOWN COMPACT and the size of the DB stay the same. I also tried SHUTDOWN with a database started with max compact time set to 5 minutes, and the DB size stay the same too. I ran both command on H2 Web UI and they both returned in less than one second.
So, I used SCRIPT/RUNSCRIPT tool as H2 document mentioned in compacting database section. The same 1.1GB database shrank to 0.5GB. However, the whole process took 40 minutes. On Sep 20, 11:48 pm, Uli <[email protected]> wrote: > Hi, > > today I dropped my complete database and run a SHUTDOWN COMPACT. I was > surprised because after the SHUTDOWN COMPACT was finished the database > files were still 3GB large. All subsequent SHUTDOWN COMPACTs did not > change that. > > I am wondering if this is a well known behaviour or if that's an > issue. The documentation tells me "re-creating the database may > further reduce the database size". I would not expect that the > difference between two empty databases could be 3GB. > > Uli -- 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.
