Mon Jul 27 02:49:24 PDT 2009
- Previous message: [Slony1-general] sl_status incorrectly reports long event lag
- Next message: [Slony1-general] Helpful admin Tools referral : scripts manager
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Skipped content of type multipart/alternative-------------- next part -----= --------- Listing 1. cluster_setup.sh = #!/bin/sh CLUSTER=3Dsql_cluster DB1=3Dcontactdb DB2=3Dcontactdb_slave H1=3D (IP) H2=3D (IP) U=3Dpostgres slonik <<_EOF_ cluster name =3D $CLUSTER; node 1 admin conninfo =3D 'dbname=3D$DB1 host=3D$H1 user=3D$U'; node 2 admin conninfo =3D 'dbname=3D$DB2 host=3D$H2 user=3D$U'; init cluster (id =3D 1, comment =3D 'Node 1'); create set (id =3D 1, origin =3D 1, comment =3D 'contact table'); set add table (set id =3D 1, origin =3D 1, id =3D 1, full qualified name =3D 'public.contact', comment =3D 'Table contact'); set add sequence (set id =3D 1, origin =3D 1, id =3D 2, full qualified name =3D 'public.contact_seq', comment =3D 'Sequence contact_seq'); store node (id =3D 2, comment =3D 'Node 2'); store path (server =3D 1, client =3D 2, conninfo =3D 'dbname=3D$DB1 host=3D$H1 user=3D$U'); store path (server =3D 2, client =3D 1, conninfo =3D 'dbname=3D$DB2 host=3D$H2 user=3D$U'); store listen (origin =3D 1, provider =3D 1, receiver =3D 2); store listen (origin =3D 2, provider =3D 2, receiver =3D 1);
- Previous message: [Slony1-general] sl_status incorrectly reports long event lag
- Next message: [Slony1-general] Helpful admin Tools referral : scripts manager
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the Slony1-general mailing list