Update of /home/cvsd/slony1/slony1-engine/doc/adminguide
In directory main.slony.info:/tmp/cvs-serv1425/doc/adminguide

Modified Files:
      Tag: REL_2_0_STABLE
	adminscripts.sgml 
Log Message:
Revised slonik dump script based on input from our DBA group...
It now uses tsort to determine the subscription ordering, so should
work even with fairly sophisticated cascaded subscriptions


Index: adminscripts.sgml
===================================================================
RCS file: /home/cvsd/slony1/slony1-engine/doc/adminguide/adminscripts.sgml,v
retrieving revision 1.52.2.3
retrieving revision 1.52.2.4
diff -C2 -d -r1.52.2.3 -r1.52.2.4
*** adminscripts.sgml	10 Jun 2009 21:11:56 -0000	1.52.2.3
--- adminscripts.sgml	12 Jun 2009 22:42:13 -0000	1.52.2.4
***************
*** 778,785 ****
  <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>
  
--- 778,783 ----
  <listitem><para> Subscriptions </para> 
  
! <para> Note that the subscriptions are ordered topologically, using
! <command>tsort</command> </para></listitem>
  </itemizedlist>
  
***************
*** 811,817 ****
  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>
--- 809,813 ----
  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.  </para>
  
  </sect2>