Hi, Sorry for the private posting - it was a mistake. Now I know why my posts haven't appeared here - erroneously I clicked 'Reply to author' instead of 'Reply'.
Back to the business: I created an index for the BLOB column of my big table: CREATE INDEX IF NOT EXISTS CONTENT_INDEX ON TABLE(CONTENT) The operation took 27557765 ms (for a DB of size as specified in my first post) and now the DB closing is virtually instant. Unfortunately another problem emerged: now insert time is more than twice as long as it was previously. This is a disaster and cosidering the two: (1) long closing time (2) long insert time I choose long closing time. So regarding the fix you propose (automatic index creation for LOB columns): will there be an option to have it disabled? I never do any SELECTs with the BLOB column involved in WHERE clause. Or perhaps would it be possible to specify that the index shall use only the first N characters of a BLOB (as done by MySQL: http://dev.mysql.com/doc/refman/5.5/en/column-indexes.html). On the other side I doubt if that helps in my case: I store files and all of them have a common header. So specifying the N first bytes is not enough, there should be possibility to specify their offset as well... Regards, wburzyns -- 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.
