db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Kristian Waagan (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (DERBY-4115) Provide a way to drop statistics information
Date Tue, 24 Apr 2012 09:55:34 GMT

    [ https://issues.apache.org/jira/browse/DERBY-4115?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13260399#comment-13260399

Kristian Waagan commented on DERBY-4115:

> Next, I plan to write upgrade test to make sure that this method will not be available
on pre-10.9 dbs, soft=upgraded dbs. It should only be available on hard upgraded dbs. 

It's been a while since I looked into upgrade and stored procedures. Does the restriction
above come from the fact that we can't support the alternative behavior? That would be to
allow the procedure to be called on a soft upgraded database to remove orphaned statistics,
and then continue using the older version afterwards. This way the problem can be fixed without
moving off the current Derby version.
Even if the above is technically possible, I'm fine with forbidding it if it conflicts with
our current policy. I was just a bit curious :)
> 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:
>            Reporter: Kathey Marsden
>            Assignee: Mamta A. Satoor
>         Attachments: DERBY4115_patch1_diff.txt
> 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


View raw message