From 4b08bf8ce7a7515f669ce0a1ce1946c6492b65ed Mon Sep 17 00:00:00 2001
From: Peter Eisentraut <peter_e@gmx.net>
Date: Mon, 2 May 2011 19:19:48 +0300
Subject: [PATCH] Small cleanup of spacing in verbatim DocBook elements
---
doc/src/sgml/recovery-config.sgml | 2 +-
doc/src/sgml/ref/pg_basebackup.sgml | 18 +++++++++---------
doc/src/sgml/tablefunc.sgml | 22 +++++++++++-----------
3 files changed, 21 insertions(+), 21 deletions(-)
diff --git a/doc/src/sgml/recovery-config.sgml b/doc/src/sgml/recovery-config.sgml
index 144b880f423..de6090520db 100644
--- a/doc/src/sgml/recovery-config.sgml
+++ b/doc/src/sgml/recovery-config.sgml
@@ -95,7 +95,7 @@ restore_command = 'copy "C:\\server\\archivedir\\%f" "%p"' # Windows
The <xref linkend="pgarchivecleanup"> module
is often used in <varname>archive_cleanup_command</> for
single-standby configurations, for example:
-<programlisting> archive_cleanup_command = 'pg_archivecleanup /mnt/server/archivedir %r' </programlisting>
+<programlisting>archive_cleanup_command = 'pg_archivecleanup /mnt/server/archivedir %r'</programlisting>
Note however that if multiple standby servers are restoring from the
same archive directory, you will need to ensure that you do not delete
WAL files until they are no longer needed by any of the servers.
diff --git a/doc/src/sgml/ref/pg_basebackup.sgml b/doc/src/sgml/ref/pg_basebackup.sgml
index 382effdaa39..26f290464c7 100644
--- a/doc/src/sgml/ref/pg_basebackup.sgml
+++ b/doc/src/sgml/ref/pg_basebackup.sgml
@@ -388,26 +388,26 @@ PostgreSQL documentation
To create a base backup of the server at <literal>mydbserver</literal>
and store it in the local directory
<filename>/usr/local/pgsql/data</filename>:
- <screen>
- <prompt>$</prompt> <userinput>pg_basebackup -h mydbserver -D /usr/local/pgsql/data</userinput>
- </screen>
+<screen>
+<prompt>$</prompt> <userinput>pg_basebackup -h mydbserver -D /usr/local/pgsql/data</userinput>
+</screen>
</para>
<para>
To create a backup of the local server with one maximum compressed
tar file for each tablespace, and store it in the directory
<filename>backup</filename>, showing a progress report while running:
- <screen>
- <prompt>$</prompt> <userinput>pg_basebackup -D backup -Ft -Z9 -P</userinput>
- </screen>
+<screen>
+<prompt>$</prompt> <userinput>pg_basebackup -D backup -Ft -Z9 -P</userinput>
+</screen>
</para>
<para>
To create a backup of a single-tablespace local database and compress
this with <productname>bzip2</productname>:
- <screen>
- <prompt>$</prompt> <userinput>pg_basebackup -D - -Ft | bzip2 > backup.tar.bz2</userinput>
- </screen>
+<screen>
+<prompt>$</prompt> <userinput>pg_basebackup -D - -Ft | bzip2 > backup.tar.bz2</userinput>
+</screen>
(this command will fail if there are multiple tablespaces in the
database)
</para>
diff --git a/doc/src/sgml/tablefunc.sgml b/doc/src/sgml/tablefunc.sgml
index dfb932f501a..60f0b57cd92 100644
--- a/doc/src/sgml/tablefunc.sgml
+++ b/doc/src/sgml/tablefunc.sgml
@@ -431,17 +431,17 @@ crosstab(text source_sql, text category_sql)
For example, <parameter>source_sql</parameter> might produce a set
something like:
<programlisting>
- SELECT row_name, extra_col, cat, value FROM foo ORDER BY 1;
-
- row_name extra_col cat value
- ----------+------------+-----+---------
- row1 extra1 cat1 val1
- row1 extra1 cat2 val2
- row1 extra1 cat4 val4
- row2 extra2 cat1 val5
- row2 extra2 cat2 val6
- row2 extra2 cat3 val7
- row2 extra2 cat4 val8
+SELECT row_name, extra_col, cat, value FROM foo ORDER BY 1;
+
+ row_name extra_col cat value
+----------+------------+-----+---------
+ row1 extra1 cat1 val1
+ row1 extra1 cat2 val2
+ row1 extra1 cat4 val4
+ row2 extra2 cat1 val5
+ row2 extra2 cat2 val6
+ row2 extra2 cat3 val7
+ row2 extra2 cat4 val8
</programlisting>
</para>
--
GitLab