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

Modified Files:
	slonik_ref.sgml 
Log Message:
a) Mention a bottleneck where having Very Large table IDs leads to memory
   bloat

b) Discuss effective use of WAIT FOR EVENT


Index: slonik_ref.sgml
===================================================================
RCS file: /home/cvsd/slony1/slony1-engine/doc/adminguide/slonik_ref.sgml,v
retrieving revision 1.87
retrieving revision 1.88
diff -C2 -d -r1.87 -r1.88
*** slonik_ref.sgml	23 Jun 2008 16:04:55 -0000	1.87
--- slonik_ref.sgml	27 Jun 2008 20:17:17 -0000	1.88
***************
*** 279,283 ****
      <para>
       Describes how the <application>slonik</application> utility can
!      reach a nodes database in the cluster from where it is run
       (likely the DBA's workstation). The conninfo string is the string
       agrument given to the <function>PQconnectdb()</function> libpq
--- 279,283 ----
      <para>
       Describes how the <application>slonik</application> utility can
!      reach a node's database in the cluster from where it is run
       (likely the DBA's workstation). The conninfo string is the string
       agrument given to the <function>PQconnectdb()</function> libpq
***************
*** 1381,1390 ****
  
  	 <para> Note that &slony1; generates an in-memory array
! 	 indicating all of the fully qualified table node; if you use
! 	 large table ID numbers, this leads to wastage of memory.
! 	 Each potential table ID consumes a pointer to a char,
! 	 commonly costing 4 bytes per table ID on 32 bit
! 	 architectures, and 8 bytes per table ID on 64 bit
! 	 architectures. </para>
  
           </listitem>
--- 1381,1390 ----
  
  	 <para> Note that &slony1; generates an in-memory array
! 	 indicating all of the fully qualified table names; if you use
! 	 large table ID numbers, the sparsely-utilized array can lead
! 	 to substantial wastage of memory.  Each potential table ID
! 	 consumes a pointer to a char, commonly costing 4 bytes per
! 	 table ID on 32 bit architectures, and 8 bytes per table ID on
! 	 64 bit architectures. </para>
  
           </listitem>
***************
*** 2828,2839 ****
      
      <para> <application>Slonik</application> remembers the last event
!      generated on every node during script execution (events generated
!      by earlier calls are currently not checked). In certain situations
!      it is necessary that events generated on one node (such as
!      <command>CREATE SET</command>) are processed on another node
!      before issuing more commands (for instance, <xref
!       linkend="stmtsubscribeset">).  <command>WAIT FOR EVENT</command> may be
!      used to cause the <application>slonik</application> script to wait
!      until the subscriber node is ready for the next action.
      </para>
      
--- 2828,2840 ----
      
      <para> <application>Slonik</application> remembers the last event
!     generated on every node during script execution (events generated
!     by earlier calls are currently not checked). In certain situations
!     it is necessary that events generated on one node (such as
!     <command>CREATE SET</command>) are processed on another node
!     before issuing more commands (for instance, <xref
!     linkend="stmtsubscribeset">).  <command>WAIT FOR EVENT</command>
!     may be used to cause the <application>slonik</application> script
!     to wait for confirmation of an event, which hopefully means that
!     the subscriber node is ready for the next action.
      </para>
      
***************
*** 2903,2907 ****
     linkend="slonik"> script that <xref linkend="stmtsubscribeset"> is
     complete, you may submit a <xref linkend="stmtsync"> event after
!    the subscription, and have the WAIT request wait on that
     <command>SYNC</command> event, as follows. </para>
      <programlisting>
--- 2904,2908 ----
     linkend="slonik"> script that <xref linkend="stmtsubscribeset"> is
     complete, you may submit a <xref linkend="stmtsync"> event after
!    the subscription, and have the WAIT request wait on the
     <command>SYNC</command> event, as follows. </para>
      <programlisting>