Tue Aug 25 10:17:59 PDT 2009
- Previous message: [Slony1-commit] slony1-engine/tools/altperl slon_status.pl
- Next message: [Slony1-commit] slony1-engine/doc/adminguide slonik_ref.sgml
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Update of /home/cvsd/slony1/slony1-engine/doc/adminguide
In directory main.slony.info:/tmp/cvs-serv9106/doc/adminguide
Modified Files:
Tag: REL_2_0_STABLE
slonik_ref.sgml
Log Message:
Clarify that the EVENT NODE for STORE NODE must be an existing node, not
the newly-added node.
Index: slonik_ref.sgml
===================================================================
RCS file: /home/cvsd/slony1/slony1-engine/doc/adminguide/slonik_ref.sgml,v
retrieving revision 1.92.2.7
retrieving revision 1.92.2.8
diff -C2 -d -r1.92.2.7 -r1.92.2.8
*** slonik_ref.sgml 17 Jun 2009 21:37:38 -0000 1.92.2.7
--- slonik_ref.sgml 25 Aug 2009 17:17:57 -0000 1.92.2.8
***************
*** 557,566 ****
<varlistentry><term><literal> EVENT NODE = ival </literal></term>
! <listitem><para> The ID of the node used to create the configuration
! event that tells all existing nodes about the new node.
! </para></listitem>
! </varlistentry>
! </variablelist>
! </para>
<para> This uses &funinitializelocalnode; and &funenablenode;. </para>
--- 557,565 ----
<varlistentry><term><literal> EVENT NODE = ival </literal></term>
! <listitem><para> The ID of the node used to create the
! configuration event that tells all existing nodes about the
! new node. It must be the ID of a pre-existing node in the
! cluster, not the ID of the new node. </para></listitem>
! </varlistentry> </variablelist> </para>
<para> This uses &funinitializelocalnode; and &funenablenode;. </para>
- Previous message: [Slony1-commit] slony1-engine/tools/altperl slon_status.pl
- Next message: [Slony1-commit] slony1-engine/doc/adminguide slonik_ref.sgml
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the Slony1-commit mailing list