Dan Karp wrote:
I think we may be getting hit with DERBY-269 (stale index cardinality causes table scans).  The 
command listed in that JIRA ("alter table <table-name> compress [sequential]") 
isn't valid.  Calling SYSCS_UTIL.SYSCS_COMPRESS_TABLE works, but takes a huge amount of CPU, 
disk I/O, and disk space.  Is there a simpler, straightforward way to force recalculation of 
these indexes?

https://issues.apache.org/jira/browse/DERBY-269

According to the documentation: Cardinality statistics are updated when a table scan is performed so a " select * from <table> " should do it.


Reply via email to