Chris Browne cbbrowne at lists.slony.info
Thu Nov 29 13:37:48 PST 2007
Update of /home/cvsd/slony1/slony1-engine/doc/adminguide
In directory main.slony.info:/tmp/cvs-serv7165

Modified Files:
	slonik_ref.sgml 
Log Message:
Add notes to INIT CLUSTER about maximum sizing of cluster name


Index: slonik_ref.sgml
===================================================================
RCS file: /home/cvsd/slony1/slony1-engine/doc/adminguide/slonik_ref.sgml,v
retrieving revision 1.74
retrieving revision 1.75
diff -C2 -d -r1.74 -r1.75
*** slonik_ref.sgml	22 Oct 2007 20:49:26 -0000	1.74
--- slonik_ref.sgml	29 Nov 2007 21:37:46 -0000	1.75
***************
*** 463,468 ****
     CLUSTER </command> does not need to draw configuration from other
     existing nodes.
- 
     </para> </note>
     </refsect1>
     <refsect1> <title> Locking Behaviour </title>
--- 463,475 ----
     CLUSTER </command> does not need to draw configuration from other
     existing nodes.
     </para> </note>
+ 
+    <note> <para> Be aware that some objects are created that contain
+    the cluster name as part of their name.  (Notably, partial indexes
+    on <envar>sl_log_1</envar> and <envar>sl_log_2</envar>.)  As a
+    result, <emphasis>really long</emphasis> cluster names are a bad
+    idea, as they can make object names <quote>blow up</quote> past the
+    typical maximum name length of 63 characters. </para> </note>
+ 
     </refsect1>
     <refsect1> <title> Locking Behaviour </title>



More information about the Slony1-commit mailing list