Re: [h2] SHUTDOWN COMPACT does not recover space SHUTDOWN DEFRAG take insanely long Opening DB takes 500Mb of space

2016-11-24 Thread Petr Holík | EgoPanda
Hello Thomas, it makes a sense we are using CLOBs in our database extensively. And it often ends with Missing LOB entry(which i've reported on github) or database with wasted space (after deleting data mostly from table which contains CLOBs). Propably is something broken in H2 in handling (C)LOB.

Re: [h2] SHUTDOWN COMPACT does not recover space SHUTDOWN DEFRAG take insanely long Opening DB takes 500Mb of space

2016-11-24 Thread Thomas Mueller Graf
Hi, It could be due to LOG data (BLOB, CLOB) that are not referenced, and not correctly garbage collected. To analyze that, we would need a reproducible test case. To find out, you could use the Recover tool on the large database. Regards, Thomas On Tuesday, November 22, 2016, Petr Holík wro

Re: [h2] SHUTDOWN COMPACT does not recover space SHUTDOWN DEFRAG take insanely long Opening DB takes 500Mb of space

2016-11-24 Thread Thomas Mueller Graf
Hi, It could be due to LOG data (BLOB, CLOB) that are not referenced, and not correctly garbage collected. To analyze that, we would need a reproducible test case. To find out, you could use the Recover tool on the large database. Regards, Thomas On Tuesday, November 22, 2016, Petr Holík wro

[h2] SHUTDOWN COMPACT does not recover space SHUTDOWN DEFRAG take insanely long Opening DB takes 500Mb of space

2016-11-21 Thread Petr Holík
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 openi