db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Mike Matrigali <mikem_...@sbcglobal.net>
Subject Re: [PATCH] Derby 218 - Add relaxed durability option
Date Wed, 11 May 2005 16:35:55 GMT
I committed this change with svn 169538.

Sunitha Kambhampati wrote:
> Mike Matrigali wrote:
> 
>> Could you resolve the conflict in LogToFile.java in the current trunk
>> revision and resubmit the patch?
>>
> I resolved the conflict and regenerated the 
> patch(DurabilityTest_0510.txt). Let me know if you have any problems 
> applying this patch.
> 
> Thanks,
> Sunitha.
> 
>> Sunitha Kambhampati wrote:
>>
>>> Thanks Suresh for your comments.  I have attached a new patch that 
>>> takes care of them and as well as the property name change as 
>>> discussed on the list.
>>>
>>> So now,
>>> 1)To enable this no syncs mode, the property setting  is 
>>> derby.system.durability=test  If it is set to any other value other 
>>> than test, then this property setting is ignored and the system will 
>>> default to the usual mode where all syncs happen correctly.
>>> 2) If database is booted in this mode then the  flag  to indicate 
>>> this mode is being used is set in log.ctrl file and it will not 
>>> change after that.Thus there wont be any switching between this mode 
>>> ( no syncs) to default ( all syncs) mode because we cannot guarantee 
>>> that the database will be in a consistent state once its booted in 
>>> this no sync mode..
>>> 3) This  flag is now written out as part of the log control flags in 
>>> log.ctrl file instead of using a spare byte.
>>> _______________________
deleted rest ...


Mime
View raw message