Mark Stosberg <[EMAIL PROTECTED]> writes: > Hello, > > I suggest that these references that refer to "COPY SET" be updated to > refer to "SUBSCRIBE SET": > > # grep -R 'COPY SET' faq.sgml slonik_ref.sgml startslons.sgml > faq.sgml:Further hurting performane, the <command>COPY SET</command> event > > slonik_ref.sgml: the <command>COPY SET</command> process winds up > doing more work than should be > > startslons.sgml:initial <command>COPY SET</command>. The problem that > came up in that > > startslons.sgml:restarting slon, thereby restarting the <command>COPY > SET</command> > > startslons.sgml:<command>COPY SET</command> in progress.</para>
I have clarified this; I think it *is* relevant to mention COPY SET, as it is an event distinct from the subscription request. But as you observed, it is something that the user does not expressly request, which occurs as part of the work of a SUBSCRIBE SET request. Switching over to SUBSCRIBE SET would make the material in startslons.sgml much more confusing, unfortunately. > Referring to COPY SET without a connection to how it is triggered is > confusing. Right. -- let name="cbbrowne" and tld="ca.afilias.info" in String.concat "@" [name;tld];; <http://dba2.int.libertyrms.com/> Christopher Browne (416) 673-4124 (land) _______________________________________________ Slony1-general mailing list [email protected] http://gborg.postgresql.org/mailman/listinfo/slony1-general
