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] Updated: (DERBY-4771) Continue investigation of automatic creation/update of index statistics
Date Thu, 09 Sep 2010 11:40:32 GMT

     [ https://issues.apache.org/jira/browse/DERBY-4771?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel

Kristian Waagan updated DERBY-4771:

    Attachment: derby-4771-1b-prototype_code_dump.diff

Attaching patch revision 1b.

Thanks for having a look at the patch, Lily.
Seems a last minute change caused a lot of trouble. Early on the I think I ignored all exceptions
originating from IndexStatisticsDaemon.writeUpdatedStats, but before I uploaded the patch
I added checks for specific errors.
I have added another check for the container opened in read-only mode error. The issue I see
is that Derby doesn't detect that the database is read-only before it's too late to disable
the statistics update feature. I tried the isReadOnly-method on both store, lcc, and tx -
but none of those returned true at the time when the index statistics daemon is called for.
In this case the read-only was caused by missing file privileges, maybe Derby will handle
other causes better (?).

If you run the tests again with patch 1b, hopefully all you'll see is four failures in lang.OrderByAndSortAvoidance
(two distinct failures).

> Continue investigation of automatic creation/update of index statistics
> -----------------------------------------------------------------------
>                 Key: DERBY-4771
>                 URL: https://issues.apache.org/jira/browse/DERBY-4771
>             Project: Derby
>          Issue Type: Task
>            Reporter: Kristian Waagan
>         Attachments: derby-4771-1a-prototype_code_dump.diff, derby-4771-1a-prototype_code_dump.stat,
derby-4771-1b-prototype_code_dump.diff, rjall.out
> Work was started to improve Derby's handling of index statistics. This issue tracks further
discussion and work for this task.

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

View raw message