diff options
| -rw-r--r-- | doc/src/sgml/backup.sgml | 4 | ||||
| -rw-r--r-- | doc/src/sgml/config.sgml | 4 | ||||
| -rw-r--r-- | doc/src/sgml/ecpg.sgml | 2 | ||||
| -rw-r--r-- | doc/src/sgml/high-availability.sgml | 2 | ||||
| -rw-r--r-- | doc/src/sgml/protocol.sgml | 4 |
5 files changed, 8 insertions, 8 deletions
diff --git a/doc/src/sgml/backup.sgml b/doc/src/sgml/backup.sgml index 12f2efe4e2a..2d67521775c 100644 --- a/doc/src/sgml/backup.sgml +++ b/doc/src/sgml/backup.sgml @@ -878,7 +878,7 @@ SELECT pg_start_backup('label', false, false); <application>pg_dump</application> or <application>pg_dumpall</application>). It is neither 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 consider during this backup. </para> @@ -988,7 +988,7 @@ SELECT pg_start_backup('label', true); <application>pg_dump</application> or <application>pg_dumpall</application>). It is neither 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 consider during this backup. </para> diff --git a/doc/src/sgml/config.sgml b/doc/src/sgml/config.sgml index 32c39a05165..b379b67b30a 100644 --- a/doc/src/sgml/config.sgml +++ b/doc/src/sgml/config.sgml @@ -532,10 +532,10 @@ include_dir 'conf.d' </term> <listitem> <para> - Specifies the configuration file for - <xref linkend="auth-username-maps"> user name mapping + Specifies the configuration file for user name mapping (customarily called <filename>pg_ident.conf</>). This parameter can only be set at server start. + See also <xref linkend="auth-username-maps">. </para> </listitem> </varlistentry> diff --git a/doc/src/sgml/ecpg.sgml b/doc/src/sgml/ecpg.sgml index 508406823d9..89d4c57da7d 100644 --- a/doc/src/sgml/ecpg.sgml +++ b/doc/src/sgml/ecpg.sgml @@ -1189,7 +1189,7 @@ EXEC SQL END DECLARE SECTION; There are two use cases for arrays as host variables. The first is a way to store some text string in <type>char[]</type> 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 cursor. Without an array, to process a query result consisting of multiple rows, it is required to use a cursor and diff --git a/doc/src/sgml/high-availability.sgml b/doc/src/sgml/high-availability.sgml index cc84b911b0e..51359d6236f 100644 --- a/doc/src/sgml/high-availability.sgml +++ b/doc/src/sgml/high-availability.sgml @@ -207,7 +207,7 @@ protocol to make nodes agree on a serializable transactional order. middleware. Care must also be taken that all transactions either commit or abort on all servers, perhaps 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</> are examples of this type of replication. </para> diff --git a/doc/src/sgml/protocol.sgml b/doc/src/sgml/protocol.sgml index 7c82b488459..244e381de9a 100644 --- a/doc/src/sgml/protocol.sgml +++ b/doc/src/sgml/protocol.sgml @@ -2296,8 +2296,8 @@ The commands accepted in walsender mode are: <para> The individual protocol messages are discussed in the following - subsections. Individual messages are describer in - <xref linkend="protocol-logicalrep-message-formats"> section. + subsections. Individual messages are described in + <xref linkend="protocol-logicalrep-message-formats">. </para> <para> |