doc: Fix some whitespace issues in the man pages

This commit is contained in:
Peter Eisentraut 2013-05-13 21:59:39 -04:00
parent d2b920cded
commit a9bb274f90
3 changed files with 20 additions and 22 deletions

View File

@ -693,8 +693,7 @@ pgbench <optional> <replaceable>options</> </optional> <replaceable>dbname</>
through its standard output. through its standard output.
</para> </para>
<para> <para><replaceable>argument</> can be either a text constant or a
<replaceable>argument</> can be either a text constant or a
<literal>:</><replaceable>variablename</> reference to a variable of <literal>:</><replaceable>variablename</> reference to a variable of
any types. If you want to use <replaceable>argument</> starting with any types. If you want to use <replaceable>argument</> starting with
colons, you need to add an additional colon at the beginning of colons, you need to add an additional colon at the beginning of

View File

@ -299,8 +299,7 @@ PostgreSQL documentation
directory output format because this is the only output format where multiple processes directory output format because this is the only output format where multiple processes
can write their data at the same time. can write their data at the same time.
</para> </para>
<para> <para><application>pg_dump</> will open <replaceable class="parameter">njobs</replaceable>
<application>pg_dump</> will open <replaceable class="parameter">njobs</replaceable>
+ 1 connections to the database, so make sure your <xref linkend="guc-max-connections"> + 1 connections to the database, so make sure your <xref linkend="guc-max-connections">
setting is high enough to accommodate all connections. setting is high enough to accommodate all connections.
</para> </para>

View File

@ -180,32 +180,32 @@ PostgreSQL documentation
<para> <para>
Standard Usage: Standard Usage:
<screen> <screen>
<prompt>$</prompt> <userinput>pg_isready</userinput> <prompt>$</prompt> <userinput>pg_isready</userinput>
<computeroutput>/tmp:5432 - accepting connections</computeroutput> <computeroutput>/tmp:5432 - accepting connections</computeroutput>
<prompt>$</prompt> <userinput>echo $?</userinput> <prompt>$</prompt> <userinput>echo $?</userinput>
<computeroutput>0</computeroutput> <computeroutput>0</computeroutput>
</screen> </screen>
</para> </para>
<para> <para>
Running with connection parameters to a <productname>PostgreSQL</productname> cluster in startup: Running with connection parameters to a <productname>PostgreSQL</productname> cluster in startup:
<screen> <screen>
<prompt>$ </prompt><userinput>pg_isready -h localhost -p 5433</userinput> <prompt>$ </prompt><userinput>pg_isready -h localhost -p 5433</userinput>
<computeroutput>localhost:5433 - rejecting connections</computeroutput> <computeroutput>localhost:5433 - rejecting connections</computeroutput>
<prompt>$</prompt> <userinput>echo $?</userinput> <prompt>$</prompt> <userinput>echo $?</userinput>
<computeroutput>1</computeroutput> <computeroutput>1</computeroutput>
</screen> </screen>
</para> </para>
<para> <para>
Running with connection parameters to a non-responsive <productname>PostgreSQL</productname> cluster: Running with connection parameters to a non-responsive <productname>PostgreSQL</productname> cluster:
<screen> <screen>
<prompt>$ </prompt><userinput>pg_isready -h someremotehost</userinput> <prompt>$ </prompt><userinput>pg_isready -h someremotehost</userinput>
<computeroutput>someremotehost:5432 - no response</computeroutput> <computeroutput>someremotehost:5432 - no response</computeroutput>
<prompt>$</prompt> <userinput>echo $?</userinput> <prompt>$</prompt> <userinput>echo $?</userinput>
<computeroutput>2</computeroutput> <computeroutput>2</computeroutput>
</screen> </screen>
</para> </para>
</refsect1> </refsect1>