db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Suresh Thalamati <suresh.thalam...@gmail.com>
Subject Re: [jira] Created: (DERBY-218) Add Relaxed Durability option
Date Tue, 12 Apr 2005 19:06:13 GMT
Sunitha Kambhampati (JIRA) wrote:

>Add Relaxed Durability option 
>         Key: DERBY-218
>         URL: http://issues.apache.org/jira/browse/DERBY-218
>     Project: Derby
>        Type: Improvement
>  Components: Store  
>    Versions:    
> Environment: all
>    Reporter: Sunitha Kambhampati
>     Fix For:
>Dan Debrunner posted a fix to allow for relaxed durability changes in http://article.gmane.org/gmane.comp.apache.db.derby.user/681/match=relaxed+durability
>1) Need to add this option in Derby maybe as some property
>2) Also from discussions on the list, Mike suggested that 
>- that the logging system be changed to somehow
>record that the database has operated in this manner, so that if
>the database goes corrupt we don't waste effort trying to figure out
>what when wrong.  Probably need some way to mark the log records, the
>log control file and write a message to the user error log file.
How about  adding  in-memory support for Derby instead of  trying to 
confuse the users with relaxed durabilty option.
In this mode ,  will the database be  recoverable to some consistent 
state always with  possible loss of  some transaction data in
case of a crash ?

View raw message