[jira] Commented: (DERBY-3551) Implement procedure SYSCS_UTIL.SYSCS_PREPARE_REPLICATION()

["V.Narayanan (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/DERBY-3551?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12580259#action_12580259 ] 

V.Narayanan commented on DERBY-3551:
------------------------------------

I have been trying to understand how I can enable logging for unlogged operations. 
My guide so far has been JIRA comments and code related to DERBY-239 - 
Need a online backup feature that does not block update operations when online backup 
is in progress.

Derby-239 enables logging for unlogged operations by turning on the logArchived mode.
Turning on logArchived mode from my understanding, archives logs as well as logs unlogged
operations.

But for replication archiving of logs is not necessary, we need to only turn on the logging.

I am investigating further on how this alone can be done.

> Implement procedure SYSCS_UTIL.SYSCS_PREPARE_REPLICATION()
> ----------------------------------------------------------
>
>                 Key: DERBY-3551
>                 URL: https://issues.apache.org/jira/browse/DERBY-3551
>             Project: Derby
>          Issue Type: Sub-task
>          Components: Replication
>    Affects Versions: 10.4.0.0, 10.5.0.0
>            Reporter: V.Narayanan
>            Assignee: V.Narayanan
>
> Jorgen says-
> I suggest that the replication step in which the master database is frozen is replaced by a new system procedure to solve index and import:
> Old: SYSCS_UTIL.SYSCS_FREEZE_DATABASE()
> New: SYSCS_UTIL.SYSCS_PREPARE_REPLICATION()
> The new system procedure should:
> 1) Freeze the database
> 2) Check if there are any ongoing transactions with unlogged operations. If so - unfreeze and abort. Otherwise:
> 3) Enable logging of unlogged operations 

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.