database/postgres
database/postgres
1
0
Fork 0
mirror of https://github.com/postgres/postgres.git synced 2025-04-21 12:05:57 +03:00
Code

doc: Fix a few typos and awkward links

Browse Source
This commit is contained in:
Peter Eisentraut 2017-03-18 23:43:47 -04:00
parent e3044f6184
commit 767ce36ff3
5 changed files with 8 additions and 8 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
doc/src/sgml/backup.sgml
View File

@ -878,7 +878,7 @@ SELECT pg_start_backup('label', false, false);
<application>pg_dump</application> or <application>pg_dump</application> or
<application>pg_dumpall</application>). It is neither <application>pg_dumpall</application>). It is neither
necessary nor desirable to stop normal operation of the database necessary nor desirable to stop normal operation of the database
while you do this. See section while you do this. See
<xref linkend="backup-lowlevel-base-backup-data"> for things to <xref linkend="backup-lowlevel-base-backup-data"> for things to
consider during this backup. consider during this backup.
</para> </para>
@ -988,7 +988,7 @@ SELECT pg_start_backup('label', true);
<application>pg_dump</application> or <application>pg_dump</application> or
<application>pg_dumpall</application>). It is neither <application>pg_dumpall</application>). It is neither
necessary nor desirable to stop normal operation of the database necessary nor desirable to stop normal operation of the database
while you do this. See section while you do this. See
<xref linkend="backup-lowlevel-base-backup-data"> for things to <xref linkend="backup-lowlevel-base-backup-data"> for things to
consider during this backup. consider during this backup.
</para> </para>

4
doc/src/sgml/config.sgml
View File

@ -532,10 +532,10 @@ include_dir 'conf.d'
</term> </term>
<listitem> <listitem>
<para> <para>
Specifies the configuration file for Specifies the configuration file for user name mapping
<xref linkend="auth-username-maps"> user name mapping
(customarily called <filename>pg_ident.conf</>). (customarily called <filename>pg_ident.conf</>).
This parameter can only be set at server start. This parameter can only be set at server start.
See also <xref linkend="auth-username-maps">.
</para> </para>
</listitem> </listitem>
</varlistentry> </varlistentry>

2
doc/src/sgml/ecpg.sgml
View File

@ -1189,7 +1189,7 @@ EXEC SQL END DECLARE SECTION;
There are two use cases for arrays as host variables. The first There are two use cases for arrays as host variables. The first
is a way to store some text string in <type>char[]</type> is a way to store some text string in <type>char[]</type>
or <type>VARCHAR[]</type>, as or <type>VARCHAR[]</type>, as
explained <xref linkend="ecpg-char">. The second use case is to explained in <xref linkend="ecpg-char">. The second use case is to
retrieve multiple rows from a query result without using a retrieve multiple rows from a query result without using a
cursor. Without an array, to process a query result consisting cursor. Without an array, to process a query result consisting
of multiple rows, it is required to use a cursor and of multiple rows, it is required to use a cursor and

2
doc/src/sgml/high-availability.sgml
View File

@ -207,7 +207,7 @@ protocol to make nodes agree on a serializable transactional order.
middleware. Care must also be taken that all middleware. Care must also be taken that all
transactions either commit or abort on all servers, perhaps transactions either commit or abort on all servers, perhaps
using two-phase commit (<xref linkend="sql-prepare-transaction"> using two-phase commit (<xref linkend="sql-prepare-transaction">
and <xref linkend="sql-commit-prepared">. and <xref linkend="sql-commit-prepared">).
<productname>Pgpool-II</> and <productname>Continuent Tungsten</> <productname>Pgpool-II</> and <productname>Continuent Tungsten</>
are examples of this type of replication. are examples of this type of replication.
</para> </para>

4
doc/src/sgml/protocol.sgml
View File

@ -2296,8 +2296,8 @@ The commands accepted in walsender mode are:
<para> <para>
The individual protocol messages are discussed in the following The individual protocol messages are discussed in the following
subsections. Individual messages are describer in subsections. Individual messages are described in
<xref linkend="protocol-logicalrep-message-formats"> section. <xref linkend="protocol-logicalrep-message-formats">.
</para> </para>
<para> <para>