Hi, > I dont know, but wouldn't it be great if one were able to chose > whether one wants a cached or in-memory index?
You are right. Currently, indexes of temporary tables are always in-memory indexes. I think that's a good default, but I will change the parser so that persistent indexes are supported as well using the syntax: create cached global temporary table test2(name varchar primary key); And of course the DROP TABLE will not be required in the next release. > I'm still wondering why the in-memory index is >10 times larger I don't think it's always "10 times". Because the index is kept in memory, in most cases the rows are also kept in memory. The memory requirement of in-memory indexes depends on the number of rows in the table. The memory requirement of b-tree indexes only depends on the cache size. Regard, Thomas -- 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.
