Thu Jun 11 12:03:46 PDT 2009
- Previous message: [Slony1-commit] slony1-engine RELEASE RELEASE-2.0 config.h.in configure
- Next message: [Slony1-commit] slony1-engine/src/slon cleanup_thread.c confoptions.c misc.c scheduler.c
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Update of /home/cvsd/slony1/slony1-engine/doc/adminguide In directory main.slony.info:/tmp/cvs-serv5001/doc/adminguide Modified Files: Makefile adminscripts.sgml failover.sgml faq.sgml firstdb.sgml installation.sgml monitoring.sgml Log Message: Draw a whole pile of changes into HEAD from the 2.0 branch Index: Makefile =================================================================== RCS file: /home/cvsd/slony1/slony1-engine/doc/adminguide/Makefile,v retrieving revision 1.21 retrieving revision 1.22 diff -C2 -d -r1.21 -r1.22 *** Makefile 20 Feb 2009 15:47:22 -0000 1.21 --- Makefile 11 Jun 2009 19:03:44 -0000 1.22 *************** *** 74,84 **** install: installdirs ifdef docdir for file in man1/*.1; do \ ! $(INSTALL_DATA) $$file $(DESTDIR)$(mandir)/man1/$$file || exit;\ done for file in man7/*.7; do \ ! echo $$file \ ! $(INSTALL_DATA) $$file $(DESTDIR)$(mandir)/man7/$$file || exit;\ done for file in $(wildcard *.html) stylesheet.css ; do \ --- 74,85 ---- install: installdirs + ifdef D2MSCRIPT ifdef docdir for file in man1/*.1; do \ ! $(INSTALL_DATA) $$file $(DESTDIR)$(mandir)/$$file || exit;\ done for file in man7/*.7; do \ ! echo $$file; \ ! $(INSTALL_DATA) "$$file" $(DESTDIR)$(mandir)/$$file || exit;\ done for file in $(wildcard *.html) stylesheet.css ; do \ *************** *** 86,89 **** --- 87,91 ---- done endif + endif .PHONY: html Index: adminscripts.sgml =================================================================== RCS file: /home/cvsd/slony1/slony1-engine/doc/adminguide/adminscripts.sgml,v retrieving revision 1.54 retrieving revision 1.55 diff -C2 -d -r1.54 -r1.55 *** adminscripts.sgml 30 Apr 2009 16:07:47 -0000 1.54 --- adminscripts.sgml 11 Jun 2009 19:03:44 -0000 1.55 *************** *** 759,762 **** --- 759,819 ---- </sect2> + <sect2 id="slonikconfdump"> <title>slonikconfdump.sh</title> + + <indexterm><primary>slonik configuration dump</primary></indexterm> + + <para> The tool <filename>tools/slonikconfdump.sh</filename> was + created to help dump out a &lslonik; script to duplicate the + configuration of a functioning &slony1; cluster.</para> + + <para> It dumps out: </para> + + <itemizedlist> + <listitem><para>Cluster name </para> </listitem> + <listitem><para>Node connection information </para> <para> Note that it uses the first value it finds (<emphasis>e.g.</emphasis> - for the lowest numbered client node). </para> </listitem> + <listitem><para> Nodes </para> </listitem> + <listitem><para> Sets </para> </listitem> + <listitem><para> Tables </para> </listitem> + <listitem><para> Sequences </para> </listitem> + <listitem><para> Subscriptions </para> + + <para> Note that the subscriptions are ordered by set, then by + provider, then by receiver. This ordering does not necessarily + indicate the order in which subscriptions need to be + applied. </para></listitem> + </itemizedlist> + + <para> It may be run as follows: </para> + <programlisting> + chris at dba2:Slony-I/CMD/slony1-2.0/tools> SLONYCLUSTER=slony_regress1 PGDATABASE=slonyregress1 bash slonikconfdump.sh + # building slonik config files for cluster slony_regress1 + # generated by: slonikconfdump.sh + # Generated on: Tue Jun 9 17:34:12 EDT 2009 + cluster name=slony_regress1; + include <admin-conninfos.slonik>; # Draw in ADMIN CONNINFO lines + node 1 admin conninfo='dbname=slonyregress1 host=localhost user=chris port=7083'; + node 2 admin conninfo='dbname=slonyregress2 host=localhost user=chris port=7083'; + init cluster (id=1, comment='Regress test node'); + store node (id=2, comment='node 2'); + store path (server=1, client=2, conninfo='dbname=slonyregress1 host=localhost user=chris port=7083', connretry=10); + store path (server=2, client=1, conninfo='dbname=slonyregress2 host=localhost user=chris port=7083', connretry=10); + create set (id=1, origin=1, comment='All test1 tables'); + set add table (id=1, set id=1, origin=1, fully qualified name='"public"."table1"', comment='accounts table, key='table1_pkey'); + set add table (id=2, set id=1, origin=1, fully qualified name='"public"."table2"', comment='public.table2, key='table2_id_key'); + set add table (id=4, set id=1, origin=1, fully qualified name='"public"."table4"', comment='a table of many types, key='table4_pkey'); + set add table (id=5, set id=1, origin=1, fully qualified name='"public"."table5"', comment='a table with composite PK strewn across the table, key='table5_pkey'); + subscribe set (id=1, provider=1, receiver=2, forward=YES); + chris at dba2:Slony-I/CMD/slony1-2.0/tools> + </programlisting> + + <para> The output should be reviewed before it is applied elsewhere. + Particular attention should be paid to the <command>ADMIN + CONNINFO</command>, as it picks the first value that it sees for each + node; in a complex environment, where visibility of nodes may vary + from subnet to subnet, it may not pick the right value. In addition, + <command>SUBSCRIBE SET</command> statements do not necessarily + indicate the order in which subscriptions need to be applied.</para> + + </sect2> </sect1> <!-- Keep this comment at the end of the file
- Previous message: [Slony1-commit] slony1-engine RELEASE RELEASE-2.0 config.h.in configure
- Next message: [Slony1-commit] slony1-engine/src/slon cleanup_thread.c confoptions.c misc.c scheduler.c
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the Slony1-commit mailing list