Wed Jun 10 14:11:58 PDT 2009
- Previous message: [Slony1-commit] slony1-engine/src/slon scheduler.c
- Next message: [Slony1-commit] slony1-engine/tools slonikconfdump.sh
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Update of /home/cvsd/slony1/slony1-engine/doc/adminguide
In directory main.slony.info:/tmp/cvs-serv18169/doc/adminguide
Modified Files:
Tag: REL_2_0_STABLE
adminscripts.sgml
Log Message:
Change ordering of subscription extraction, and document the restrictions
a bit more carefully for the configuration dumper
Index: adminscripts.sgml
===================================================================
RCS file: /home/cvsd/slony1/slony1-engine/doc/adminguide/adminscripts.sgml,v
retrieving revision 1.52.2.2
retrieving revision 1.52.2.3
diff -C2 -d -r1.52.2.2 -r1.52.2.3
*** adminscripts.sgml 9 Jun 2009 21:38:27 -0000 1.52.2.2
--- adminscripts.sgml 10 Jun 2009 21:11:56 -0000 1.52.2.3
***************
*** 776,780 ****
<listitem><para> Tables </para> </listitem>
<listitem><para> Sequences </para> </listitem>
! <listitem><para> Subscriptions </para> </listitem>
</itemizedlist>
--- 776,785 ----
<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>
***************
*** 802,810 ****
</programlisting>
! <para> The output should be reviewed before it is applied elsewhere;
! particular attention should be paid to the <command>ADMIN
! CONNINFO</command> statements, as it picks the first value that it
! sees for each node; in a complex environment, it may not pull out the
! right value.</para>
</sect2>
--- 807,817 ----
</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>
- Previous message: [Slony1-commit] slony1-engine/src/slon scheduler.c
- Next message: [Slony1-commit] slony1-engine/tools slonikconfdump.sh
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the Slony1-commit mailing list