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

Modified Files:
	cluster.sgml faq.sgml slonik_ref.sgml 
Log Message:
Document that node numbers are immutable by intent.

Also, fix docs to CLONE commands to indicate that these are new in
v2.0, not v1.2


Index: cluster.sgml
===================================================================
RCS file: /home/cvsd/slony1/slony1-engine/doc/adminguide/cluster.sgml,v
retrieving revision 1.15
retrieving revision 1.16
diff -C2 -d -r1.15 -r1.16
*** cluster.sgml	8 Apr 2008 22:12:27 -0000	1.15
--- cluster.sgml	11 Apr 2008 14:55:14 -0000	1.16
***************
*** 24,30 ****
  
  <para> Note that, as recorded in the <xref linkend="faq"> under <link
! linkend="cannotrenumbernodes"> How can I renumber nodes?</link>, it is
! not particularly possible to change a node's node number after it has
! been set up.</para>
  
  <para>Some planning should be done, in more complex cases, to ensure
--- 24,30 ----
  
  <para> Note that, as recorded in the <xref linkend="faq"> under <link
! linkend="cannotrenumbernodes"> How can I renumber nodes?</link>, the
! node number is immutable, so it is not possible to change a node's
! node number after it has been set up.</para>
  
  <para>Some planning should be done, in more complex cases, to ensure

Index: slonik_ref.sgml
===================================================================
RCS file: /home/cvsd/slony1/slony1-engine/doc/adminguide/slonik_ref.sgml,v
retrieving revision 1.83
retrieving revision 1.84
diff -C2 -d -r1.83 -r1.84
*** slonik_ref.sgml	27 Mar 2008 19:55:40 -0000	1.83
--- slonik_ref.sgml	11 Apr 2008 14:55:14 -0000	1.84
***************
*** 511,516 ****
       <variablelist>
        <varlistentry><term><literal>ID = ival</literal></term>
!       <listitem><para> The unique, numeric ID number of the new
!       node.</para></listitem>
        </varlistentry>
        
--- 511,520 ----
       <variablelist>
        <varlistentry><term><literal>ID = ival</literal></term>
!       <listitem><para> The unique, immutable numeric ID number of the new
!       node.</para>
! 
!       <para> Note that the ID is <emphasis>immutable</emphasis>
!       because it is used as the basis for inter-node event
!       communications. </para> </listitem>
        </varlistentry>
        
***************
*** 3063,3067 ****
     </Refsect1>
     <refsect1> <title> Version Information </title>
!     <para> This command was introduced in &slony1; 1.2.0. </para>
     </refsect1>
    </Refentry>
--- 3067,3071 ----
     </Refsect1>
     <refsect1> <title> Version Information </title>
!     <para> This command was introduced in &slony1; 2.0. </para>
     </refsect1>
    </Refentry>
***************
*** 3101,3105 ****
     </Refsect1>
     <refsect1> <title> Version Information </title>
!     <para> This command was introduced in &slony1; 1.2.0. </para>
     </refsect1>
    </Refentry>
--- 3105,3109 ----
     </Refsect1>
     <refsect1> <title> Version Information </title>
!     <para> This command was introduced in &slony1; 2.0. </para>
     </refsect1>
    </Refentry>

Index: faq.sgml
===================================================================
RCS file: /home/cvsd/slony1/slony1-engine/doc/adminguide/faq.sgml,v
retrieving revision 1.76
retrieving revision 1.77
diff -C2 -d -r1.76 -r1.77
*** faq.sgml	8 Apr 2008 22:12:27 -0000	1.76
--- faq.sgml	11 Apr 2008 14:55:14 -0000	1.77
***************
*** 347,354 ****
  
  <answer> <para> The first answer is <quote>you can't do that</quote> -
! &slony1; node numbers are not particularly amenable to being
! <quote>changed.</quote> Node numbers are deeply woven into the fibres
! of the schema, by virtue of being written into virtually every table
! in the system, and by virtue of being used as the basis for event
  propagation.  The only time that it might be <quote>OK</quote> to
  modify a node number is at some time where we know that it is not in
--- 347,354 ----
  
  <answer> <para> The first answer is <quote>you can't do that</quote> -
! &slony1; node numbers are quite <quote>immutable.</quote> Node numbers
! are deeply woven into the fibres of the schema, by virtue of being
! written into virtually every table in the system, but much more
! importantly by virtue of being used as the basis for event
  propagation.  The only time that it might be <quote>OK</quote> to
  modify a node number is at some time where we know that it is not in
***************
*** 357,363 ****
  
  <para> To do this in an automated fashion seems like a
! <emphasis>huge</emphasis> challenge, as it spontaneously changes the
! structure of the very event propagation system that is required for
! such a change to propagate.</para> </answer>
  
  <answer> <para> If it is <emphasis>enormously necessary</emphasis> to
--- 357,363 ----
  
  <para> To do this in an automated fashion seems like a
! <emphasis>huge</emphasis> challenge, as it changes the structure of
! the very event propagation system that already needs to be working in
! order for such a change to propagate.</para> </answer>
  
  <answer> <para> If it is <emphasis>enormously necessary</emphasis> to