[h2] SHUTDOWN COMPACT does not recover space SHUTDOWN DEFRAG take insanely long Opening DB takes 500Mb of space
Hello, 1.4.192 db, Page Store 1.7GB -> SHUTDOWN COMPACT -> 1.4GB -> open -> 1.9GB -> SHUTDOWN DEFRAG -> takes on cpu thread(3.5Ghz for maybe two three minutes) -> SHUTDOWN COMPACT -> 1.4GB -> export to SQL ~60MB sql -> import -> ~60MB DB file Why compact does almost not compact and why opening db takes 500Mb of space? I have not investigated ho much data process realy writes to db when opening it.(on SSD it looks fast but on rotation disk it takes ages to open DB) Sincerely Petr Holik -- 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 post to this group, send email to h2-database@googlegroups.com. Visit this group at https://groups.google.com/group/h2-database. For more options, visit https://groups.google.com/d/optout.
Re: [h2] Data stored in the INFORMATION_SCHEMA.LOBS and INFORMATION_SCHEMA.LOB_MAP tables seems to blow up our database
Thanks Noel for you answer. We will try to track down the code / SQL statement that causes the growth. What is in your opinion the best approach to do so? I was thinking to write some code that monitors the database file size and logs any size change. I would also log any SQL statement sent to the database. Doing so I hope we can see a relation between a SQL statement and the file growth. -- 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 post to this group, send email to h2-database@googlegroups.com. Visit this group at https://groups.google.com/group/h2-database. For more options, visit https://groups.google.com/d/optout.
