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