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

Modified Files:
	cluster.sgml faq.sgml testbed.sgml 
Log Message:
Fix SGML tagging problem in testbed.sgml, and add commentary indicating
the challenges of renumbering nodes.


Index: cluster.sgml
===================================================================
RCS file: /home/cvsd/slony1/slony1-engine/doc/adminguide/cluster.sgml,v
retrieving revision 1.14
retrieving revision 1.15
diff -C2 -d -r1.14 -r1.15
*** cluster.sgml	25 Feb 2008 15:37:58 -0000	1.14
--- cluster.sgml	8 Apr 2008 22:12:27 -0000	1.15
***************
*** 23,26 ****
--- 23,31 ----
  node #1, and for the subscriber to be node #2.</para>
  
+ <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
  that the numbering system is kept sane, lest the administrators be

Index: testbed.sgml
===================================================================
RCS file: /home/cvsd/slony1/slony1-engine/doc/adminguide/testbed.sgml,v
retrieving revision 1.17
retrieving revision 1.18
diff -C2 -d -r1.17 -r1.18
*** testbed.sgml	7 Apr 2008 20:47:48 -0000	1.17
--- testbed.sgml	8 Apr 2008 22:12:27 -0000	1.18
***************
*** 147,150 ****
--- 147,151 ----
  </glossentry>
  
+ <glossentry>
  <glossterm><envar>TMPDIR</envar></glossterm>
  

Index: faq.sgml
===================================================================
RCS file: /home/cvsd/slony1/slony1-engine/doc/adminguide/faq.sgml,v
retrieving revision 1.75
retrieving revision 1.76
diff -C2 -d -r1.75 -r1.76
*** faq.sgml	27 Mar 2008 18:21:58 -0000	1.75
--- faq.sgml	8 Apr 2008 22:12:27 -0000	1.76
***************
*** 341,344 ****
--- 341,370 ----
  
  </qandaentry>
+ 
+ <qandaentry id="cannotrenumbernodes">
+ <question> <para> I'd like to renumber the node numbers in my cluster.
+ How can I renumber nodes? </para> </question>
+ 
+ <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
+ use, and we would need to do updates against each node in the cluster
+ in an organized fashion.</para>
+ 
+ <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
+ renumber nodes, this might be accomplished by dropping and re-adding
+ nodes to get rid of the node formerly using the node ID that needs to
+ be held by another node.</para> </answer>
+ </qandaentry>
+ 
  <qandadiv>