Daniel John Debrunner (JIRA) wrote:
Is the functional spec updated to reflect the new names of the procedures?
Not yet. I will update.
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.
hmm... did not think user could interpret NOWAIT this way too.
Following two new procedures, now includes NOWAIT:
SYSCS_BACKUP_DATABASE_NOWAIT(..)
SYSCS_BACKUP_DATABASE_AND_ENABLE_LOG_ARCHIVE_MODE_NOWAIT(..).
These two procedures will throw error , if there are any uncommitted
unlogged operation before stating the backup. They will not wait for
the unlogged operations to complete unlike
SYSCS_BACKUP_DATABASE and
SYSCS_BACKUP_DATABASE_AND_ENABLE_LOG_ARCHIVE_MODE
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.
I agree. Any suggestions ?
Other alternatives were :
SYSCS_ONLINE_BACKUP_DATABASE (... IN WAIT SMALLINT) and
SYSCS_ONLINE_BACKUP_DATABASE_AND_ENABLE_LOG_ARCHIVE_MODE(...IN WAIT
SMALLINT)
users need to pass non-zero value to wait for unlogged operations ,
otherwise, procedures will throw error if there any unlogged operations.
Thanks
-suresht
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.
