index
:
monkeysphere
autoquote
dualquote
master
rootsquash
shell
Unnamed repository; edit this file 'description' to name the repository.
Jonas Smedegaard
summary
refs
log
tree
commit
diff
log msg
author
committer
range
path:
root
/
website
diff options
context:
1
2
3
4
5
6
7
8
README
------------
$Id$
Christopher Browne
cbbrowne@gmail.com
2006-09-29
------------
The script configure-replication.sh is intended to allow the gentle user
to readily configure replication of the LedgerSMB database schema
using the Slony-I replication system for PostgreSQL.
For more general details about Slony-I, see <http://slony.info/>
This script uses a number of environment variables to determine the
shape of the configuration. In many cases, the defaults should be at
least nearly OK...
Global:
CLUSTER - Name of Slony-I cluster
NUMNODES - Number of nodes to set up
PGUSER - name of PostgreSQL superuser controlling replication
PGPORT - default port number
PGDATABASE - default database name
For each node, there are also four parameters; for node 1:
DB1 - database to connect to
USER1 - superuser to connect as
PORT1 - port
HOST1 - host
It is quite likely that DB*, USER*, and PORT* should be drawn from the
default PGDATABASE, PGUSER, and PGPORT values above; that sort of
uniformity is usually a good thing.
In contrast, HOST* values should be set explicitly for HOST1, HOST2,
..., as you don't get much benefit from the redundancy replication
provides if all your databases are on the same server!
slonik config files are generated in a temp directory under /tmp. The
usage is thus:
1. preamble.slonik is a "preamble" containing connection info used by
the other scripts.
Verify the info in this one closely; you may want to keep this
permanently to use with other maintenance you may want to do on the
cluster.
2. create_set.slonik
This is the first script to run; it sets up the requested nodes as
being Slony-I nodes, adding in some Slony-I-specific config tables
and such.
You can/should start slon processes any time after this step has run.
3. store_paths.slonik
This is the second script to run; it indicates how the slons
should intercommunicate. It assumes that all slons can talk to
all nodes, which may not be a valid assumption in a
complexly-firewalled environment.
4. create_set.slonik
This sets up the replication set consisting of the whole bunch of
tables and sequences that make up the LedgerSMB database schema.
