Tue Mar 21 11:07:06 PST 2006
- Previous message: [Slony1-commit] By cbbrowne: Add in -x option - command_on_logarchive Upon completing a
- Next message: [Slony1-commit] By cbbrowne: Add in documentation for slon "-x" option to run program
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Log Message:
-----------
locking.sgml - note that locks on tables apply to the SUBSCRIBER, not to
the provider/origin.
Modified Files:
--------------
slony1-engine/doc/adminguide:
locking.sgml (r1.7 -> r1.8)
-------------- next part --------------
Index: locking.sgml
===================================================================
RCS file: /usr/local/cvsroot/slony1/slony1-engine/doc/adminguide/locking.sgml,v
retrieving revision 1.7
retrieving revision 1.8
diff -Ldoc/adminguide/locking.sgml -Ldoc/adminguide/locking.sgml -u -w -r1.7 -r1.8
--- doc/adminguide/locking.sgml
+++ doc/adminguide/locking.sgml
@@ -72,6 +72,12 @@
subscription. By locking the tables early, this means that the
subscription cannot fail after copying some of the data due to some
other process having held on to a table. </para>
+
+<para> In any case, note that this one began with the wording
+<quote>on a new subscriber.</quote> The locks are applied <emphasis>on
+the new subscriber.</emphasis> They are <emphasis>not</emphasis>
+applied on the provider or on the origin. </para>
+
</listitem>
</itemizedlist>
- Previous message: [Slony1-commit] By cbbrowne: Add in -x option - command_on_logarchive Upon completing a
- Next message: [Slony1-commit] By cbbrowne: Add in documentation for slon "-x" option to run program
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the Slony1-commit mailing list