</programlisting>

<para>

Alternatively, you can specify a particular query type to reset by

providing its hash value in the <literal>fspase_hash</literal> option. For example:

providing its hash value in the <literal>fspace_hash</literal> option. For example:

</para>

<programlisting>

DELETE FROM aqo_data WHERE fspace_hash = (SELECT fspace_hash FROM aqo_queries

There can be more than one <literal>host</literal> parameter in

the connection string. In this case these hosts would be considered

alternate entries into same database and if connection to first one

fails, the second would beattemped, and so on. This can be used

fails, the second would beattempted, and so on. This can be used

for high availability clusters or for load balancing. See the

<xref linkend="libpq-connect-hostorder"> parameter. This feature

works for TCP/IP host names only.

specified in the <xref linkend="libpq-connect-host"> parameter.

</para>

<para>

If the value of this argument is <literal>sequential</literal> (the

default) connections to the hosts will be attempted in the order in

If the value of this argument is <literal>sequential</literal>

(default), connections to the hosts will be attempted in the order in

which they are specified.

</para>

<para>

several cluster nodes. However, PostgreSQL doesn't currently support

multimaster clusters. So, without the use of third-party products,

only read-only connections can take advantage from

load-balancing. See <xref linkend="libpq-connect-target-server-type">

load-balancing. See <xref linkend="libpq-connect-target-server-type">.

</para>

</listitem>

</varlistentry>

<term><literal>failover_timeout</literal></term>

<listitem>

<para>

Maximum time to cyclically retry all the hosts in the connection string.

Maximum time to cyclically retry all the hosts in the connection string

(as decimal integer number of seconds). If not specified, then

hosts are tried just once.

</para>

<para>

The name of the column by which to perform table partitioning. It is recommended to choose partitioning keys of the following types:</para>

<itemizedlist>

<listitem><para><type>text</type>of <type>integer</type> data types for hash partitioning</para></listitem>

<listitem><para><type>text</type>or <type>integer</type> data types for hash partitioning</para></listitem>

<listitem><para>numeric or date/time data types for range partitioning</para></listitem>

</itemizedlist>

</listitem>

<term><option>--xid=<replaceable class="parameter">START_XID</replaceable></option></term>

<listitem>

<para>

Specifies a start xid value in the decimal for new db instance to test 64-bit xids,

Specifies a start xid value in the decimalformatfor new db instance to test 64-bit xids,

default value is <literal>0</literal>.

</para>

</listitem>