1
0
mirror of https://github.com/postgres/postgres.git synced 2025-06-27 23:21:58 +03:00

doc: Fix a few typos and awkward links

This commit is contained in:
Peter Eisentraut
2017-03-18 23:44:30 -04:00
parent b04edf249c
commit 10a3637eaf
3 changed files with 4 additions and 4 deletions

View File

@ -280,10 +280,10 @@ SET ENABLE_SEQSCAN TO OFF;
</indexterm>
<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>

View File

@ -1160,7 +1160,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

View File

@ -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>