---
name: "SLONIK_INIT_CLUSTER"
section: "7"
platform: "linux"
package: "slony1-2-doc"
version: "2.2.11-6"
release: "Debian 13 (Trixie)"
platforms: ["linux"]
url: "https://new.carta.tech/SLONIK_INIT_CLUSTER"
---

# SLONIK\_INIT\_CLUSTER(7)

Initialize Slony-I cluster

## NAME

INIT CLUSTER - Initialize Slony-I cluster

## SYNOPSIS

FC**INIT CLUSTER**F\[0\]  \[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\].

- FCIDF\[0\]

  The unique, numeric ID number of the node.

- FCCOMMENT = 'comment text'F\[0\]

  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

```
FCINIT CLUSTER (
   ID = 1,
   COMMENT = 'Node 1'
);
    F[0]
```

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