Details
-
Improvement
-
Status: Closed
-
Major
-
Resolution: Fixed
-
10.6.1.0
-
High Value Fix
Description
Now that DERBY-269 has been resolved, users can update statistics, but once they do, they are committed to using and maintaining the statistics, even if it doesn't improve performance or they have difficulty maintaining the statistics on a regular basis. It would be good to have a way to drop statistics information so that users could revert to the prior behavior if needed.
Attachments
Attachments
Issue Links
- is related to
-
DERBY-5681 When a foreign key constraint on a table is dropped, the associated statistics row for the conglomerate is not removed
- Closed
-
DERBY-269 Provide some way to update index cardinality statistics (e.g. reimplement update statistics)
- Closed