[ http://issues.apache.org/jira/browse/DERBY-239?page=comments#action_12363275 ]
Daniel John Debrunner commented on DERBY-239: --------------------------------------------- Is the functional spec updated to reflect the new names of the procedures? I'm actually confused as to why the name now includes NOWAIT, not sure what the NOWAIT is meant to imply to the user of the procedures. To me it might seem that this would imply the procedure returns right away and the backup continues in the background. Hopefully an updated functional spec will make it clear why NOWAIT is part of the name. For Derby to be easy to use the names of the system procedures should clearly indicate what they do. > Need a online backup feature that does not block update operations when > online backup is in progress. > -------------------------------------------------------------------------------------------------------- > > Key: DERBY-239 > URL: http://issues.apache.org/jira/browse/DERBY-239 > Project: Derby > Type: New Feature > Components: Store > Versions: 10.1.1.0 > Reporter: Suresh Thalamati > Assignee: Suresh Thalamati > Attachments: obtest_customer.jar, onlinebackup.html, onlinebackup1.html, > onlinebackup_1.diff, onlinebackup_2.diff, onlinebackup_3.diff, > onlinebackup_4.diff, onlinebackup_5.diff, onlinebackup_6.diff, > onlinebackup_7.diff > > Currently Derby allows users to perfoms online backups using > SYSCS_UTIL.SYSCS_BACKUP_DATABASE() procedure, but while the backup is in > progress, update operations are temporarily blocked, but read operations can > still proceed. > Blocking update operations can be real issue specifically in client server > environments, because user requests will be blocked for a long time if a > backup is in the progress on the server. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
