On Mon, Mar 20, 2006 at 02:15:08PM -0500, Christopher Browne wrote: > > * During the COPY_SET event on a new subscriber > > In a sense, this is the least provocative scenario, since, before the > > replication set has been populated, it is pretty reasonable to say > > that the node is "unusable" and that Slony-I could reasonably demand > > exclusive access to the node. > > [...] > > If you can suggest where that section of the documentation could be made > clearer, that would be useful, and I'd be more than happy to improve that.
Probably worth mentioning that the lock only happens on the subscriber, even though it's somewhat redundant. IE: that the node is "unusable" and that Slony-I could reasonably demand exclusive access to the node. Note that this lock takes place only on the subscriber, and not the origin. -- Jim C. Nasby, Sr. Engineering Consultant [EMAIL PROTECTED] Pervasive Software http://pervasive.com work: 512-231-6117 vcard: http://jim.nasby.net/pervasive.vcf cell: 512-569-9461 _______________________________________________ Slony1-general mailing list [email protected] http://gborg.postgresql.org/mailman/listinfo/slony1-general
