Wed Nov 9 23:19:37 PST 2005
- Previous message: [Slony1-commit] By cbbrowne: Note (per Vivek Khera) that LOCK SET waits for old
- Next message: [Slony1-commit] By cbbrowne: Start adding documentation on the new generation test bed
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Log Message:
-----------
Add mention in SET ADD TABLE that the table ID number needs to be
unique, including across sets.
Modified Files:
--------------
slony1-engine/doc/adminguide:
slonik_ref.sgml (r1.31 -> r1.32)
-------------- next part --------------
Index: slonik_ref.sgml
===================================================================
RCS file: /usr/local/cvsroot/slony1/slony1-engine/doc/adminguide/slonik_ref.sgml,v
retrieving revision 1.31
retrieving revision 1.32
diff -Ldoc/adminguide/slonik_ref.sgml -Ldoc/adminguide/slonik_ref.sgml -u -w -r1.31 -r1.32
--- doc/adminguide/slonik_ref.sgml
+++ doc/adminguide/slonik_ref.sgml
@@ -1125,7 +1125,11 @@
these numbers should represent any applicable table hierarchy
to make sure the <application>slonik</application> command
scripts do not deadlock at any critical
- moment.</para></listitem>
+ moment.</para>
+
+ <para> This ID must be unique across all sets; you cannot
+ have two tables in the same cluster with the same
+ ID. </para></listitem>
</varlistentry>
<varlistentry><term><literal> FULLY QUALIFIED NAME = 'string' </literal></term>
<listitem><para> The full table name as described in
- Previous message: [Slony1-commit] By cbbrowne: Note (per Vivek Khera) that LOCK SET waits for old
- Next message: [Slony1-commit] By cbbrowne: Start adding documentation on the new generation test bed
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the Slony1-commit mailing list