SLONIK_INIT_CLUSTER man page on DragonFly

Man page or keyword search:  
man Server   44335 pages
apropos Keyword Search (all sections)
Output format
DragonFly logo
[printable version]

SLONIK INIT CLUSTER(7) Configuration and Action commandsSLONIK INIT CLUSTER(7)

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 initializelocalnode(integer,text) and enablenode(integer).

       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.

       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 Post‐
       greSQL 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

				18 January 2015		SLONIK INIT CLUSTER(7)
[top]

List of man pages available for DragonFly

Copyright (c) for man pages and the logo by the respective OS vendor.

For those who want to learn more, the polarhome community provides shell access and support.

[legal] [privacy] [GNU] [policy] [cookies] [netiquette] [sponsors] [FAQ]
Tweet
Polarhome, production since 1999.
Member of Polarhome portal.
Based on Fawad Halim's script.
....................................................................
Vote for polarhome
Free Shell Accounts :: the biggest list on the net