[
https://issues.apache.org/jira/browse/DERBY-4115?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13244305#comment-13244305
]
Mike Matrigali commented on DERBY-4115:
---------------------------------------
Of course can't say without seeing an implementation, but I can't think of
potential issues for not implementing this. And give
DERBY-5681 it seems even more useful. One problem is I don't think we can
backport this feature, as adding a new system procedure
would create compatibility/upgrade issues. So would not help 10.8 users but
would help in the future for 10.9 and above.
And it would be great if the implementation handled the unexpected rows caused
by DERBY-5681, since even after this bug is fixed
we may always in the future still see these rows as people upgrade old dbs to
new derby versions.
> 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
