I've also experienced this slowness when dropping a large table. I spent a considerable amount of time with the H2 source code trying to find a way to speed things up, but alas it turns out not to be an easy task with the current data store.
On Thursday, 5 July 2012 13:35:17 UTC+4, wburzyns wrote: > > I did a similar experiment. My table consists of 3 columns (BIGINT NOT > NULL DEFAULT NEXT VALUE FOR GLOBAL_SEQ PRIMARY KEY, BLOB, BLOB) an > currrently has over 11*10^6 rows (total DB size is over 17 GB). > Dropping of this table was ugly slow - I interrupted it after 15 > minutes, cannot afford waiting for several hours like jarradk :) I > noticed that during the proccess the DB files have grown in size by > several GBs. Additionally 'pageStore: Transaction log could not be > truncated' appeared in the trace file. > I'm on latest-greatest version of H2. -- You received this message because you are subscribed to the Google Groups "H2 Database" group. To view this discussion on the web visit https://groups.google.com/d/msg/h2-database/-/VD5FkrFQnEkJ. 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.
