Commit a5acb7df authored by Bruce Momjian's avatar Bruce Momjian

Remove tabs from sgml.

parent e08ab7c3
<!-- $PostgreSQL: pgsql/doc/src/sgml/high-availability.sgml,v 1.42 2010/02/12 14:53:22 heikki Exp $ --> <!-- $PostgreSQL: pgsql/doc/src/sgml/high-availability.sgml,v 1.43 2010/02/13 03:38:26 momjian Exp $ -->
<chapter id="high-availability"> <chapter id="high-availability">
<title>High Availability, Load Balancing, and Replication</title> <title>High Availability, Load Balancing, and Replication</title>
...@@ -873,9 +873,9 @@ if (!triggered) ...@@ -873,9 +873,9 @@ if (!triggered)
<term><varname>restore_end_command</varname> (<type>string</type>)</term> <term><varname>restore_end_command</varname> (<type>string</type>)</term>
<listitem> <listitem>
<para> <para>
In standby-mode, <varname>restore_command</> (and <varname>restore_end_command</>) is set to a In standby-mode, <varname>restore_command</> (and <varname>restore_end_command</>) is set to a
simple command or script like in PITR. pg_standby or similar tools simple command or script like in PITR. pg_standby or similar tools
that wait for the next WAL file to arrive, cannot be used with that wait for the next WAL file to arrive, cannot be used with
streaming replication, as the server handles retries and waiting streaming replication, as the server handles retries and waiting
itself. Set <varname>restore_command</> as you would if you were itself. Set <varname>restore_command</> as you would if you were
recovering using a Continuous archiving backup (see <xref linkend="backup-pitr-recovery">). recovering using a Continuous archiving backup (see <xref linkend="backup-pitr-recovery">).
......
Markdown is supported
0% or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment