diff options
-rw-r--r-- | doc/src/sgml/pgbench.sgml | 3 | ||||
-rw-r--r-- | doc/src/sgml/ref/pg_dump.sgml | 3 | ||||
-rw-r--r-- | doc/src/sgml/ref/pg_isready.sgml | 36 |
3 files changed, 20 insertions, 22 deletions
diff --git a/doc/src/sgml/pgbench.sgml b/doc/src/sgml/pgbench.sgml index 579dfd74f86..e9900d32670 100644 --- a/doc/src/sgml/pgbench.sgml +++ b/doc/src/sgml/pgbench.sgml @@ -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 diff --git a/doc/src/sgml/ref/pg_dump.sgml b/doc/src/sgml/ref/pg_dump.sgml index 0186ce0938b..0ab69c3f667 100644 --- a/doc/src/sgml/ref/pg_dump.sgml +++ b/doc/src/sgml/ref/pg_dump.sgml @@ -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> diff --git a/doc/src/sgml/ref/pg_isready.sgml b/doc/src/sgml/ref/pg_isready.sgml index 19ff1d4935d..bef6a444155 100644 --- a/doc/src/sgml/ref/pg_isready.sgml +++ b/doc/src/sgml/ref/pg_isready.sgml @@ -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> |