Mon Nov 21 21:41:17 PST 2005
- Previous message: [Slony1-general] Re: Simple multi slave example?
- Next message: [Slony1-general] Installation layout options
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
I am still unable to assist you without the error messages that you are receiving when you run this script. Also, please direct your replies to the slony1 mailing list and not to me directly. This way, others may be able to chip in and assist you. Tim On Mon, Nov 21, 2005 at 02:10:10PM -0700, Melvin Davidson wrote: > Sorry, > > My error. I am experimenting with both Slony and PGcluster. > Here is the slony script I use. > > > Tim Goodaire wrote: > > >I've just taken a look at your scripts, and I believe I may have discovered > >your problem. These scripts appear to be for PGCluster, and not Slony. > > > >You will probably have more success troubleshooting your problem on the > >PGCluster mailing list. > > > >Tim > > > > > > > > > > slonik <<_EOF_ > > #-- > # define the namespace the replication system uses in our example it is > # slony_example > #-- > CLUSTER NAME = $REPCLUSTER; > > #-- > # admin conninfo's are used by slonik to connect to the nodes one for each > # node on each side of the cluster, the syntax is that of PQconnectdb in > # the C-API > # -- > node 1 admin conninfo = 'dbname=$MASTERDBNAME host=$MASTERHOST port=$PGPORT user=$REPLICATIONUSER'; > node 2 admin conninfo = 'dbname=$MASTERDBNAME host=$SLAVE1HOST port=$PGPORT user=$REPLICATIONUSER'; > node 3 admin conninfo = 'dbname=$MASTERDBNAME host=$SLAVE2HOST port=$PGPORT user=$REPLICATIONUSER'; > > # Initialize new cluster > # init the first node. Its id MUST be 1. This creates the schema > # _$CLUSTERNAME containing all replication system specific database > # objects. > > init cluster ( id=1, comment = 'Replication Master Node'); > > # Make new set for tables > CREATE SET (ID=1, ORIGIN=1, COMMENT = 'Rep tables'); > > # Add the tables to the set > SET ADD TABLE (SET ID=1, ORIGIN=1, ID=101, FULLY QUALIFIED NAME = 'rep_test.test_table', comment='test table'); > > #-- > # Create the second node (the slave) tell the 2 nodes how to connect to > # each other and how they should listen for events. > #-- > > store node (id=2, comment = 'Rep Slave1 node'); > store node (id=3, comment = 'Rep Slave2 node'); > > store path (server = 1, client = 2, conninfo='dbname=$MASTERDBNAME host=$MASTERHOST port=$PGPORT user=$REPLICATIONUSER '); > store path (server = 2, client = 1, conninfo='dbname=$MASTERDBNAME host=$SLAVE1HOST port=$PGPORT user=$REPLICATIONUSER '); > store path (server = 3, client = 2, conninfo='dbname=$MASTERDBNAME host=$SLAVE1HOST port=$PGPORT user=$REPLICATIONUSER '); > > store listen (origin=1, provider = 1, receiver =2); > store listen (origin=2, provider = 2, receiver =1); > store listen (origin=3, provider = 3, receiver =2); > store listen (origin=2, provider = 2, receiver =3); -- Tim Goodaire 416-673-4126 tgoodair at ca.afilias.info Database Administrator, Afilias Canada Corp. -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 187 bytes Desc: not available Url : http://gborg.postgresql.org/pipermail/slony1-general/attachments/20051121/6af6bcbe/attachment.bin
- Previous message: [Slony1-general] Re: Simple multi slave example?
- Next message: [Slony1-general] Installation layout options
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the Slony1-general mailing list