Log Message:
-----------
Improve discussion of how to define sets, notably on the distinction
between primary key, candidate PK, and not having one...

Also make Slony-II mentions a bit less certain...

Modified Files:
--------------
    slony1-engine/doc/adminguide:
        defineset.sgml (r1.22 -> r1.23)
        intro.sgml (r1.21 -> r1.22)

-------------- next part --------------
Index: defineset.sgml
===================================================================
RCS file: /usr/local/cvsroot/slony1/slony1-engine/doc/adminguide/defineset.sgml,v
retrieving revision 1.22
retrieving revision 1.23
diff -Ldoc/adminguide/defineset.sgml -Ldoc/adminguide/defineset.sgml -u -w -r1.22 -r1.23
--- doc/adminguide/defineset.sgml
+++ doc/adminguide/defineset.sgml
@@ -23,8 +23,10 @@
 <para>&slony1; <emphasis>needs</emphasis> to have a primary key or
 candidate thereof on each table that is replicated.  PK values are
 used as the primary identifier for each tuple that is modified in the
-source system.  There are three ways that you can get &slony1; to use
-a primary key:</para>
+source system.  Note that they can be composite keys composed of
+multiple NOT NULL columns; they don't need to consist of single
+fields.  There are three ways that you can get &slony1; to use a
+primary key:</para>
 
 <itemizedlist>