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] Commented: (DERBY-239) Need a online backup feature that does not block update operations when online backup is in progress.
Date Tue, 01 Nov 2005 00:21:59 GMT
Thanks for the input. I will go with the option 1.

Nested transaction may not solve this problem , Nested Transaction 
will be be on the same thread as the user thread, so user will not be 
able to commit the unlogged operations for the backup operation to 


Øystein Grøvlen wrote:
>>>>>>"MM" == Mike Matrigali <mikem_app@sbcglobal.net> writes:
>     MM> I like option 1, make sure it is well documented.  I actually lean
>     MM> toward even stronger, have the command commit the current transaction
>     MM> before and after the backup.
> Generally, I do not like such implicit commits.  It is likely to catch
> someone by surprise.  On the other, I do not think many people would
> intentionally do backup as part of a larger transaction.
> In my opinion, the ideal solution would be to execute backup in a
> nested transaction.  I do not know whether it is worth the effort.

View raw message