I have a largisch database (~6G) which I use in H2 2.1.214 embedded mode on 
an NVME SSD. I use the JDBC call

rsIdx = con.getMetaData.getIndexInfo(catalog,schema,table,false,false)

to get the indexes for a single table (which is by far the largest in the 
whole database) that contains about 3.6 million rows. The call takes about 
14 seconds to return the index es/segments for the table. On a not-so-fast 
older SSD the same call takes ~30 seconds.

Is there a reason that this takes so long? Is there a more efficient way to 
determine which indexes are present on a table?

Thanks,

Silvio

-- 
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 [email protected].
To view this discussion on the web visit 
https://groups.google.com/d/msgid/h2-database/db841c68-feca-465b-9382-ba054c379b97n%40googlegroups.com.

Reply via email to