db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Rick Hillegas (JIRA)" <j...@apache.org>
Subject [jira] [Created] (DERBY-6327) Give applications a way to request that Derby consistency-check crashed databases.
Date Fri, 30 Aug 2013 15:01:58 GMT
Rick Hillegas created DERBY-6327:
------------------------------------

             Summary: Give applications a way to request that Derby consistency-check crashed
databases.
                 Key: DERBY-6327
                 URL: https://issues.apache.org/jira/browse/DERBY-6327
             Project: Derby
          Issue Type: Improvement
          Components: SQL, Store
    Affects Versions: 10.11.0.0
            Reporter: Rick Hillegas


It is common for operating systems to scan/repair the entire file system after a machine crash.
Similarly, it may be possible/desirable for Derby to consistency-check conglomerates when
a database is booted after coming down ungracefully. A couple issues are worth considering:

1) This could be an expensive operation on a large database.

2) Derby can't tell the difference between a machine crash and an application crash.

The behavior change would be noticeable for complex, crash-prone applications with large databases.
That argues against making this the default behavior. Applications would need to opt into
this extra consistency checking.

This enhancement request comes out of a discussion on DERBY-5221.


--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Mime
View raw message