Provided by: slony1-2-doc_2.2.11-4_all bug

NAME

       CLONE PREPARE - Prepare for cloning a node.

SYNOPSIS

       clone prepare [ id] [ provider] [ comment]

DESCRIPTION

       Prepares for cloning a specified subscriber node.

       This duplicates the ‘provider’ node's configuration under a new node ID in preparation for the node to be
       copied via standard database tools.

       Note that in order that we be certain that this new node be consistent with all nodes, it is important to
       issue  a  SYNC  event  against  every node aside from the provider and wait to start copying the provider
       database at least until all those SYNC events have been confirmed  by  the  provider.  Otherwise,  it  is
       possible for the clone to miss some events.

EXAMPLE

            clone prepare (id = 33, provider = 22, comment='Clone 33');
            sync (id=11);
            sync (id=22);

SLONIK EVENT CONFIRMATION BEHAVIOUR

       Slonik  will  wait  until  the  node being cloned (the provider) is caught up with all other nodes before
       submitting the clone prepare command

VERSION INFORMATION

       This command was introduced in Slony-I 2.0.

                                                  28 July 2024                           SLONIK CLONE PREPARE(7)