NAME

       INIT CLUSTER - Initialize Slony-I cluster

SYNOPSIS

       INIT CLUSTER [ID = integer] [COMMENT = 'string']

DESCRIPTION

       Initialize the first node in a new Slony-I replication cluster. The initialization process
       consists of creating the cluster  namespace,  loading  all  the  base  tables,  functions,
       procedures   and  initializing  the  node,  using  “schemadocinitializelocalnode(p_comment
       integer,   p_local_node_id   text)”    [not    available    as    a    man    page]    and
       “schemadocenablenode(p_no_id integer)” [not available as a man page].

       ID     The unique, numeric ID number of the node.

       COMMENT = 'comment text'
              A descriptive text added to the node entry in the table “sl_node” [not available as
              a man page].

       For this process to work, the SQL scripts of the Slony-I system must be installed  on  the
       DBA workstation (the computer currently executing the slonik utility), while on the system
       where the node database is running the shared  objects  of  the  Slony-I  system  must  be
       installed  in  the  PostgreSQL library directory. Also the procedural language PL/pgSQL is
       assumed to already be installed in the target database.

EXAMPLE

       INIT CLUSTER (
          ID = 1,
          COMMENT = 'Node 1'
       );

              Note

              This command functions very similarly to SLONIK STORE NODE(7), the difference being
              that INIT CLUSTER does not need to draw configuration from other existing nodes.
              Note

              Be  aware  that  some  objects are created that contain the cluster name as part of
              their name. (Notably, partial indexes on  sl_log_1  and  sl_log_2.)  As  a  result,
              really  long  cluster names are a bad idea, as they can make object names ‘blow up’
              past the typical maximum name length of 63 characters.

LOCKING BEHAVIOUR

       This command creates a new namespace and configures  tables  therein;  no  public  objects
       should be locked during the duration of this.

SLONIK EVENT CONFIRMATION BEHAVIOUR

       Slonik does not wait for event confirmations before performing this command.

VERSION INFORMATION

       This command was introduced in Slony-I 1.0

                                        21 September 2017                  SLONIK INIT CLUSTER(7)