database/postgres
1
0
Fork 0
mirror of https://github.com/postgres/postgres.git synced 2025-07-27 12:41:57 +03:00
Code Activity

doc: Fix man page whitespace issues

Browse Source 
Whitespace between tags is significant, and in some cases it creates
extra vertical space in man pages.  The fix is to remove some newlines
in the markup.
This commit is contained in:
Peter Eisentraut
2022-04-07 18:23:28 +02:00
parent dad97e0502
commit d7ab2a9a3c
9 changed files with 15 additions and 29 deletions
Download Patch File Download Diff File Expand all files Collapse all files

3
doc/src/sgml/ref/alter_publication.sgml
View File

@ -218,8 +218,7 @@ ALTER PUBLICATION sales_publication ADD ALL TABLES IN SCHEMA marketing, sales;
<structname>production_publication</structname>:
<programlisting>
ALTER PUBLICATION production_publication ADD TABLE users, departments, ALL TABLES IN SCHEMA production;
</programlisting>
</para>
</programlisting></para>
</refsect1>
<refsect1>

3
doc/src/sgml/ref/alter_subscription.sgml
View File

@ -249,8 +249,7 @@ ALTER SUBSCRIPTION <replaceable class="parameter">name</replaceable> RENAME TO <
</para>
</listitem>
</varlistentry>
</variablelist>
</para>
</variablelist></para>
</listitem>
</varlistentry>

3
doc/src/sgml/ref/alter_table.sgml
View File

@ -923,8 +923,7 @@ WITH ( MODULUS <replaceable class="parameter">numeric_literal</replaceable>, REM
</para>
</listitem>
</varlistentry>
</variablelist>
</para>
</variablelist></para>
</listitem>
</varlistentry>

3
doc/src/sgml/ref/create_subscription.sgml
View File

@ -302,8 +302,7 @@ CREATE SUBSCRIPTION <replaceable class="parameter">subscription_name</replaceabl
</para>
</listitem>
</varlistentry>
</variablelist>
</para>
</variablelist></para>
</listitem>
</varlistentry>

8
doc/src/sgml/ref/create_trigger.sgml
View File

@ -175,12 +175,10 @@ CREATE [ OR REPLACE ] [ CONSTRAINT ] TRIGGER <replaceable class="parameter">name
</para>
<para>
<indexterm>
<primary>trigger</primary>
<secondary>constraint trigger</secondary>
</indexterm>
When the <literal>CONSTRAINT</literal> option is specified, this command creates a
<firstterm>constraint trigger</firstterm>. This is the same as a regular trigger
<firstterm>constraint trigger</firstterm>.<indexterm><primary>trigger</primary>
<secondary>constraint trigger</secondary></indexterm>
This is the same as a regular trigger
except that the timing of the trigger firing can be adjusted using
<link linkend="sql-set-constraints"><command>SET CONSTRAINTS</command></link>.
Constraint triggers must be <literal>AFTER ROW</literal> triggers on plain

3
doc/src/sgml/ref/drop_procedure.sgml
View File

@ -194,8 +194,7 @@ DROP PROCEDURE do_db_maintenance(text, text); -- potentially ambiguous
However, the last example would be ambiguous if there is also, say,
<programlisting>
CREATE PROCEDURE do_db_maintenance(IN target_schema text, IN options text) ...
</programlisting>
</para>
</programlisting></para>
</refsect1>
<refsect1 id="sql-dropprocedure-compatibility">

6
doc/src/sgml/ref/merge.sgml
View File

@ -472,11 +472,9 @@ MERGE <replaceable class="parameter">total_count</replaceable>
the action's event type.
</para>
</listitem>
</orderedlist>
</para>
</orderedlist></para>
</listitem>
</orderedlist>
</para>
</orderedlist></para>
</listitem>
<listitem>
<para>

3
doc/src/sgml/ref/pg_basebackup.sgml
View File

@ -994,8 +994,7 @@ PostgreSQL documentation
directory <filename>backup</filename>:
<screen>
<prompt>$</prompt> <userinput>pg_basebackup -D backup -Ft --compress=gzip:9</userinput>
</screen>
</para>
</screen></para>
</refsect1>

12
doc/src/sgml/ref/pgbench.sgml
View File

@ -2459,11 +2459,9 @@ END;
<para>
Here is some example output with following options:
<screen>
pgbench --aggregate-interval=10 --time=20 --client=10 --log --rate=1000
--latency-limit=10 --failures-detailed --max-tries=10 test
</screen>
<userinput>pgbench --aggregate-interval=10 --time=20 --client=10 --log --rate=1000
--latency-limit=10 --failures-detailed --max-tries=10 test</userinput>
<screen>
1649114136 5815 27552565 177846919143 1078 21716 2756787 7264696105 0 9661 0 7854 31472 4022 4022 0
1649114146 5958 28460110 182785513108 1083 20391 2539395 6411761497 0 7268 0 8127 32595 4101 4101 0
</screen>
@ -2581,8 +2579,7 @@ statement latencies in milliseconds, failures and retries:
0.582 3363 41576 UPDATE pgbench_branches SET bbalance = bbalance + :delta WHERE bid = :bid;
0.465 0 0 INSERT INTO pgbench_history (tid, bid, aid, delta, mtime) VALUES (:tid, :bid, :aid, :delta, CURRENT_TIMESTAMP);
1.933 0 0 END;
</screen>
</para>
</screen></para>
<para>
If multiple script files are specified, all statistics are reported
@ -2637,8 +2634,7 @@ statement latencies in milliseconds, failures and retries:
supposed to never occur...).
</para>
</listitem>
</itemizedlist>
</para>
</itemizedlist></para>
</listitem>
<listitem>
<para>