[
https://issues.apache.org/jira/browse/DERBY-4115?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13244029#comment-13244029
]
Kristian Waagan commented on DERBY-4115:
----------------------------------------
This seems like a simple system procedure to implement, and could be useful now
that automatic updates of index cardinality statistics is enabled by default.
We just saw a user report where the statistics were messed up due to a bug in
Derby, and this caused the istat daemon to go crazy. A bug in the daemon itself
would also be easier to work around if it is possible to discard existing
statistics after the daemon has been disabled.
Has this feature never been implemented due to lack of demand, or are there
potential issues that haven't been noted in this JIRA?
> Provide a way to drop statistics information
> --------------------------------------------
>
> Key: DERBY-4115
> URL: https://issues.apache.org/jira/browse/DERBY-4115
> Project: Derby
> Issue Type: Improvement
> Components: SQL
> Affects Versions: 10.6.1.0
> Reporter: Kathey Marsden
>
> 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.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
