Skip to content
This repository


Subversion checkout URL

You can clone with HTTPS or Subversion.

Download ZIP

Slony replication system for Postgresql

tag: REL_1_2_12

Fetching latest commit…

Cannot retrieve the latest commit at this time

$Id: README,v 1.12 2006-09-29 18:42:02 cbbrowne Exp $

Slony-I is a "master to multiple slaves" replication system with
cascading and failover.

The big picture for the development of Slony-I is a master-slave
system that includes all features and capabilities needed to replicate
large databases to a reasonably limited number of slave systems.

Slony-I is a system for data centers and backup sites, where the
normal mode of operation is that all nodes are available, and where
systems may be expected to be managed in a reasonably disciplined

1.  Build and install

    See the INSTALL file nearby

2.  Creating a sample database with application

    See the SAMPLE file nearby

    There is also a "test" directory in the source tree which contains
    a variety of regression tests.  Looking at how they work may also
    be helpful.

3.  Help!  I ran into a problem.

    The file in the documentation area named "helpitsbroken.txt"
    contains a variety of notes describing problems that people have
    run into in setting up Slony-I instances.  This has been extended
    into a full scale FAQ.

    It may be worth checking there to see if the problem you are
    having has already been documented and diagnosed by someone else.

    There is an extensive "administrative guide" in the documentation
    tree that includes manual pages for binaries and for the Slonik
    language, as well as overviews of various aspects of how Slony-I
    works and should be used, including a "Best Practices" document
    that distills some of the hard-learned lessons and a FAQ.

    This "admin guide" may be found online at:

You may also wish to contact the Slony-I mailing list, findable at
<>. or take a peek at who might be available to chat
on the IRC channel #slony on

-- Slony-I team
Something went wrong with that request. Please try again.