GSP
Quick Navigator

Search Site

Unix VPS
A - Starter
B - Basic
C - Preferred
D - Commercial
MPS - Dedicated
Previous VPSs
* Sign Up! *

Support
Contact Us
Online Help
Handbooks
Domain Status
Man Pages

FAQ
Virtual Servers
Pricing
Billing
Technical

Network
Facilities
Connectivity
Topology Map

Miscellaneous
Server Agreement
Year 2038
Credits
 

USA Flag

 

 

Man Pages


Manual Reference Pages  -  SLONIK_INIT_CLUSTER (7)

NAME

INIT CLUSTER - Initialize Slony-I cluster

CONTENTS

Synopsis

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 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

Search for    or go to Top of page |  Section 7 |  Main Index


SLONIK INIT CLUSTER (7) 18 January 2015

Powered by GSP Visit the GSP FreeBSD Man Page Interface.
Output converted with manServer 1.07.