HTTPS clone URL
Subversion checkout URL
Slony replication system for Postgresql
REL_1_0_STABLE REL_1_2_STABLE REL_2_0_STABLE REL_2_1_STABLE REL_2_2_STABLE auto_wait_for bug-141-2.0 bug-142-HEAD bug-146-HEAD bug13 bug40_steve bug40 bug78 bug104 bug115 bug117 bug120 bug124 bug125 bug126 bug128 bug137-22 bug137-squashed bug137 bug138 bug141-20 bug152 bug156 bug162 bug163 bug170 bug171 bug172 bug174 bug175 bug176 bug180 bug185 bug189 bug195 bug196 bug198 bug201 bug203 bug207 bug208 bug214 bug217 bug217_20 bug218 bug229 bug231 bug235 bug236 bug238 bug247 bug250 bug256 bug271 bug275 bug286 bug300 bug304 bug332 bug337 bug352 bug355 bulk-adding clustertest copy-protocol-22-and-bug137 copy-protocol-22 copy_freeze event_triggers fop-docs git.postgresql.org/REL_2_1_STABLE head indent-master jwieck/truncate-trigger-fix local-master/bug-134 local-master/bug148-2.0 local-master/bug148-head local_listen_failure master monitordotpy multi_node_limited multinode_review mutex_release origin/local-master/bug-134 pgxn removepre8stuff splint stevesinger/adminguide_rework stevesinger/bug136 sync_on_slaves
Nothing to show
Nothing to show
Fetching latest commit...
Cannot retrieve the latest commit at this time.
|Failed to load latest commit information.|
Slony-I ------------------ 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 fashion. 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: <http://linuxdatabases.info/info/slony.html> You may also wish to contact the Slony-I mailing list, findable at <http://slony.info/>. or take a peek at who might be available to chat on the IRC channel #slony on freenode.net. -- Slony-I team