Wed Jun 22 17:57:03 PDT 2005
- Previous message: [Slony1-commit] By cbbrowne: Added in explanations of where "slon", "slonik", "slony"
- Next message: [Slony1-commit] By devrim: Fix missing unclosed <sect2> tag.
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Log Message: ----------- Indicate that the ill effects of copying big sets only happens when the database is large. Modified Files: -------------- slony1-engine/doc/adminguide: defineset.sgml (r1.17 -> r1.18) -------------- next part -------------- Index: defineset.sgml =================================================================== RCS file: /usr/local/cvsroot/slony1/slony1-engine/doc/adminguide/defineset.sgml,v retrieving revision 1.17 retrieving revision 1.18 diff -Ldoc/adminguide/defineset.sgml -Ldoc/adminguide/defineset.sgml -u -w -r1.17 -r1.18 --- doc/adminguide/defineset.sgml +++ doc/adminguide/defineset.sgml @@ -93,7 +93,13 @@ <para> If you can split such a large set into several smaller pieces, that will shorten the length of each of the transactions, lessening -the degree of <quote>injury</quote> to performance.</para></listitem> +the degree of <quote>injury</quote> to performance.</para> + +<para> These <quote>negative effects</quote> tend to emerge when the +database being subscribed to is tens of gigabytes in size. For +relatively small databases, this shouldn't be a material factor. +</para> +</listitem> <listitem><para> Any time you invoke <xref linkend="stmtddlscript">, this requests a lock on <emphasis> every single table in the
- Previous message: [Slony1-commit] By cbbrowne: Added in explanations of where "slon", "slonik", "slony"
- Next message: [Slony1-commit] By devrim: Fix missing unclosed <sect2> tag.
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the Slony1-commit mailing list