mirror of
https://git.postgresql.org/git/postgresql.git
synced 2024-12-21 08:29:39 +08:00
doc: Fix some whitespace issues in the man pages
This commit is contained in:
parent
d2b920cded
commit
a9bb274f90
@ -693,8 +693,7 @@ pgbench <optional> <replaceable>options</> </optional> <replaceable>dbname</>
|
||||
through its standard output.
|
||||
</para>
|
||||
|
||||
<para>
|
||||
<replaceable>argument</> can be either a text constant or a
|
||||
<para><replaceable>argument</> can be either a text constant or a
|
||||
<literal>:</><replaceable>variablename</> reference to a variable of
|
||||
any types. If you want to use <replaceable>argument</> starting with
|
||||
colons, you need to add an additional colon at the beginning of
|
||||
|
@ -299,8 +299,7 @@ PostgreSQL documentation
|
||||
directory output format because this is the only output format where multiple processes
|
||||
can write their data at the same time.
|
||||
</para>
|
||||
<para>
|
||||
<application>pg_dump</> will open <replaceable class="parameter">njobs</replaceable>
|
||||
<para><application>pg_dump</> will open <replaceable class="parameter">njobs</replaceable>
|
||||
+ 1 connections to the database, so make sure your <xref linkend="guc-max-connections">
|
||||
setting is high enough to accommodate all connections.
|
||||
</para>
|
||||
|
@ -180,32 +180,32 @@ PostgreSQL documentation
|
||||
|
||||
<para>
|
||||
Standard Usage:
|
||||
<screen>
|
||||
<prompt>$</prompt> <userinput>pg_isready</userinput>
|
||||
<computeroutput>/tmp:5432 - accepting connections</computeroutput>
|
||||
<prompt>$</prompt> <userinput>echo $?</userinput>
|
||||
<computeroutput>0</computeroutput>
|
||||
</screen>
|
||||
<screen>
|
||||
<prompt>$</prompt> <userinput>pg_isready</userinput>
|
||||
<computeroutput>/tmp:5432 - accepting connections</computeroutput>
|
||||
<prompt>$</prompt> <userinput>echo $?</userinput>
|
||||
<computeroutput>0</computeroutput>
|
||||
</screen>
|
||||
</para>
|
||||
|
||||
<para>
|
||||
Running with connection parameters to a <productname>PostgreSQL</productname> cluster in startup:
|
||||
<screen>
|
||||
<prompt>$ </prompt><userinput>pg_isready -h localhost -p 5433</userinput>
|
||||
<computeroutput>localhost:5433 - rejecting connections</computeroutput>
|
||||
<prompt>$</prompt> <userinput>echo $?</userinput>
|
||||
<computeroutput>1</computeroutput>
|
||||
</screen>
|
||||
<screen>
|
||||
<prompt>$ </prompt><userinput>pg_isready -h localhost -p 5433</userinput>
|
||||
<computeroutput>localhost:5433 - rejecting connections</computeroutput>
|
||||
<prompt>$</prompt> <userinput>echo $?</userinput>
|
||||
<computeroutput>1</computeroutput>
|
||||
</screen>
|
||||
</para>
|
||||
|
||||
<para>
|
||||
Running with connection parameters to a non-responsive <productname>PostgreSQL</productname> cluster:
|
||||
<screen>
|
||||
<prompt>$ </prompt><userinput>pg_isready -h someremotehost</userinput>
|
||||
<computeroutput>someremotehost:5432 - no response</computeroutput>
|
||||
<prompt>$</prompt> <userinput>echo $?</userinput>
|
||||
<computeroutput>2</computeroutput>
|
||||
</screen>
|
||||
<screen>
|
||||
<prompt>$ </prompt><userinput>pg_isready -h someremotehost</userinput>
|
||||
<computeroutput>someremotehost:5432 - no response</computeroutput>
|
||||
<prompt>$</prompt> <userinput>echo $?</userinput>
|
||||
<computeroutput>2</computeroutput>
|
||||
</screen>
|
||||
</para>
|
||||
|
||||
</refsect1>
|
||||
|
Loading…
Reference in New Issue
Block a user