doc: Fix up spacing around verbatim DocBook elements

diff --git a/doc/src/sgml/func/func-admin.sgml b/doc/src/sgml/func/func-admin.sgml
index 24ecb46542ee2b670efc1f898a679e8a15f7eb91..72038fc835f450ecb8bd191bd2c66b53f641a990 100644 (file)
--- a/doc/src/sgml/func/func-admin.sgml
+++ b/doc/src/sgml/func/func-admin.sgml
@@ -2189,7 +2189,7 @@ SELECT pg_restore_attribute_stats(
          arguments are passed as pairs of <replaceable>argname</replaceable>
          and <replaceable>argvalue</replaceable> in the form:
 <programlisting>
- SELECT pg_restore_extended_stats(
+SELECT pg_restore_extended_stats(
     '<replaceable>arg1name</replaceable>', '<replaceable>arg1value</replaceable>'::<replaceable>arg1type</replaceable>,
     '<replaceable>arg2name</replaceable>', '<replaceable>arg2value</replaceable>'::<replaceable>arg2type</replaceable>,
     '<replaceable>arg3name</replaceable>', '<replaceable>arg3value</replaceable>'::<replaceable>arg3type</replaceable>);
@@ -2199,7 +2199,7 @@ SELECT pg_restore_attribute_stats(
          For example, to set some values for the statistics object
          <structname>myschema.mystatsobj</structname>:
 <programlisting>
- SELECT pg_restore_extended_stats(
+SELECT pg_restore_extended_stats(
     'schemaname',            'tab_schema',
     'relname',               'tab_name',
     'statistics_schemaname', 'stats_schema',

diff --git a/doc/src/sgml/func/func-window.sgml b/doc/src/sgml/func/func-window.sgml
index bcf755c9ebcab5b9cac81818a94446f70460ed72..bb41387f873c3ac1ab93a2f5af43518b3e5f680a 100644 (file)
--- a/doc/src/sgml/func/func-window.sgml
+++ b/doc/src/sgml/func/func-window.sgml
@@ -268,8 +268,8 @@
   <para>
    The <literal>null treatment</literal> option must be one of:
 <synopsis>
-  RESPECT NULLS
-  IGNORE NULLS
+RESPECT NULLS
+IGNORE NULLS
 </synopsis>
    If unspecified, the default is <literal>RESPECT NULLS</literal> which includes NULL
    values in any result calculation. <literal>IGNORE NULLS</literal> ignores NULL values.

diff --git a/doc/src/sgml/high-availability.sgml b/doc/src/sgml/high-availability.sgml
index be8d3a5bfead7ceff92db0a7f31bc2258ca70663..6d9636bd125c7fc1219af4d49ee8aa8c1c73cc60 100644 (file)
--- a/doc/src/sgml/high-availability.sgml
+++ b/doc/src/sgml/high-availability.sgml
@@ -1410,13 +1410,13 @@ synchronous_standby_names = 'ANY 2 (s1, s2, s3)'
     operations, the application retrieves the current WAL location using a
     function call like this.
 
-    <programlisting>
+<programlisting>
 postgres=# SELECT pg_current_wal_insert_lsn();
-pg_current_wal_insert_lsn
---------------------
-0/306EE20
+ pg_current_wal_insert_lsn
+---------------------------
+ 0/306EE20
 (1 row)
-    </programlisting>
+</programlisting>
    </para>
 
    <para>
@@ -1427,13 +1427,13 @@ pg_current_wal_insert_lsn
     the standby's WAL replay process reaches (or exceeds) the specified
     <acronym>LSN</acronym>.
 
-    <programlisting>
+<programlisting>
 postgres=# WAIT FOR LSN '0/306EE20';
  status
---------
+---------
  success
 (1 row)
-    </programlisting>
+</programlisting>
     Once the command returns a status of success, it guarantees that all
     changes up to the provided <acronym>LSN</acronym> have been applied,
     ensuring that subsequent read queries will reflect the latest updates.

diff --git a/doc/src/sgml/libpq.sgml b/doc/src/sgml/libpq.sgml
index 0a19c2b553b0a7260a88f6f70a8d5762c61acbbb..487997f848f2271c798aabc3dee9b2e21d84a8af 100644 (file)
--- a/doc/src/sgml/libpq.sgml
+++ b/doc/src/sgml/libpq.sgml
@@ -10648,11 +10648,11 @@ typedef struct
     development and testing. The variable accepts a comma-separated list of
     debug options:
 
-    <programlisting>
+<programlisting>
 PGOAUTHDEBUG=option1,option2,...         <lineannotation>for safe options only</lineannotation>
 PGOAUTHDEBUG=UNSAFE:option1,option2,...  <lineannotation>when using unsafe options</lineannotation>
 PGOAUTHDEBUG=UNSAFE                      <lineannotation>legacy format; enables all options</lineannotation>
-    </programlisting>
+</programlisting>
    </para>
 
    <para>
@@ -10729,11 +10729,11 @@ PGOAUTHDEBUG=UNSAFE                      <lineannotation>legacy format; enables
 
    <para>
     Examples:
-    <programlisting>
+<programlisting>
 PGOAUTHDEBUG=call-count              <lineannotation>safe options only</lineannotation>
 PGOAUTHDEBUG=UNSAFE:http,trace       <lineannotation>enable HTTP and traffic logging</lineannotation>
 PGOAUTHDEBUG=UNSAFE:http,call-count  <lineannotation>mix of unsafe and safe</lineannotation>
-    </programlisting>
+</programlisting>
    </para>
 
    <warning>

diff --git a/doc/src/sgml/maintenance.sgml b/doc/src/sgml/maintenance.sgml
index 76262df0502c2f81d5ad1e2352622948d693fd54..4a21bdb5de779b697a15c682ddeb435aba24e0b2 100644 (file)
--- a/doc/src/sgml/maintenance.sgml
+++ b/doc/src/sgml/maintenance.sgml
@@ -830,14 +830,14 @@ HINT:  Execute a database-wide VACUUM in that database.
      The <function>pg_get_multixact_stats()</function> function described in
      <xref linkend="functions-pg-snapshot"/> provides a way to monitor
      multixact allocation and usage patterns in real time, for example:
-     <programlisting>
+<screen>
 =# SELECT *, pg_size_pretty(members_size) members_size_pretty
      FROM pg_catalog.pg_get_multixact_stats();
  num_mxids | num_members | members_size | oldest_multixact | members_size_pretty
 -----------+-------------+--------------+------------------+---------------------
  311740299 |  2785241176 |  13926205880 |                2 | 13 GB
 (1 row)
-     </programlisting>
+</screen>
      This output shows a system with significant multixact activity: about
      312 million multixact IDs and about 2.8 billion member entries consuming
      13 GB of storage space.

diff --git a/doc/src/sgml/pgplanadvice.sgml b/doc/src/sgml/pgplanadvice.sgml
index 73155461c0bab2ebdbd601391df1cc1356d1a9cb..b1395ec951e642b4b36cb2814f034c9dffafdaa1 100644 (file)
--- a/doc/src/sgml/pgplanadvice.sgml
+++ b/doc/src/sgml/pgplanadvice.sgml
@@ -517,14 +517,14 @@ NO_GATHER(<replaceable>advice_target</replaceable> [ ... ])
    </para>
 
 <programlisting>
- Finalize Aggregate
-   ->  Gather
-         ->  Partial Aggregate
-               ->  Parallel Seq Scan on outer_example
-                     Filter: (something = (hashed SubPlan any_1).col1)
-                     SubPlan any_1
-                       ->  Seq Scan on inner_example
-                             Filter: (something_else > 100)
+Finalize Aggregate
+  ->  Gather
+        ->  Partial Aggregate
+              ->  Parallel Seq Scan on outer_example
+                    Filter: (something = (hashed SubPlan any_1).col1)
+                    SubPlan any_1
+                      ->  Seq Scan on inner_example
+                            Filter: (something_else > 100)
 </programlisting>
 
    <para>
@@ -534,13 +534,13 @@ NO_GATHER(<replaceable>advice_target</replaceable> [ ... ])
    </para>
 
 <programlisting>
- Aggregate
-   ->  Seq Scan on outer_example
-         Filter: (something = (hashed SubPlan any_1).col1)
-         SubPlan any_1
-           ->  Gather
-                 -> Parallel Seq Scan on inner_example
-                      Filter: (something_else > 100)
+Aggregate
+  ->  Seq Scan on outer_example
+        Filter: (something = (hashed SubPlan any_1).col1)
+        SubPlan any_1
+          ->  Gather
+                -> Parallel Seq Scan on inner_example
+                     Filter: (something_else > 100)
 </programlisting>
 
   </sect3>