Tue Jun 14 21:12:21 PDT 2005
- Previous message: [Slony1-commit] By cbbrowne: Added recommendation that people consider upgrading to PG
- Next message: [Slony1-commit] By cbbrowne: We have a resolution to the "duplicate key" problem with PG
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Log Message:
-----------
A number of formatting changes...
Modified Files:
--------------
slony1-engine/doc/adminguide:
bestpractices.sgml (r1.8 -> r1.9)
-------------- next part --------------
Index: bestpractices.sgml
===================================================================
RCS file: /usr/local/cvsroot/slony1/slony1-engine/doc/adminguide/bestpractices.sgml,v
retrieving revision 1.8
retrieving revision 1.9
diff -Ldoc/adminguide/bestpractices.sgml -Ldoc/adminguide/bestpractices.sgml -u -w -r1.8 -r1.9
--- doc/adminguide/bestpractices.sgml
+++ doc/adminguide/bestpractices.sgml
@@ -180,8 +180,7 @@
outage. </para>
</listitem>
-<listitem id="slonyuser">
-<para> &slony1;-specific user names. </para>
+<listitem id="slonyuser"> <para> &slony1;-specific user names. </para>
<para> It has proven useful to define a <command>slony</command> user
for use by &slony1;, as distinct from a generic
@@ -234,7 +233,8 @@
<para> As of version 1.1, <xref linkend="slon"> configuration may be
drawn either from the command line or from configuration files.
-<quote>Best</quote> practices have yet to emerge from the two options:</para>
+<quote>Best</quote> practices have yet to emerge from the two
+options:</para>
</listitem>
</itemizedlist>
@@ -247,16 +247,14 @@
active are visible in the process environment. (And if there are a
lot of them, they may be a nuisance to read.)</para>
-<para> Unfortunately, if you
-invoke <xref linkend="slon"> from the command line, you could
-<emphasis>forget</emphasis> to include <link linkend="logshipping">
-log shipping </link> configuration and thereby destroy the sequence of
-logs for a log shipping node. </para>
+<para> Unfortunately, if you invoke <xref linkend="slon"> from the
+command line, you could <emphasis>forget</emphasis> to include <link
+linkend="logshipping"> log shipping </link> configuration and thereby
+destroy the sequence of logs for a log shipping node. </para>
</listitem>
-<listitem>
-<para> Unlike when command line options are used, the active
-options are <emphasis>not</emphasis> visible. They can only be
+<listitem> <para> Unlike when command line options are used, the
+active options are <emphasis>not</emphasis> visible. They can only be
inferred from the name and/or contents of the <xref linkend="slon">
configuration file, and will not reflect subsequent changes to the
configuration file. </para>
- Previous message: [Slony1-commit] By cbbrowne: Added recommendation that people consider upgrading to PG
- Next message: [Slony1-commit] By cbbrowne: We have a resolution to the "duplicate key" problem with PG
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the Slony1-commit mailing list