than the client's.

This parameter can only be set in the <filename>postgresql.conf</filename>

file or on the server command line.

The default is <literal>true</literal>.

The default is <literal>on</literal>.

</para>

<para>

This parameter determines whether the passphrase command set by

<varname>ssl_passphrase_command</varname> will also be called during a

configuration reload if a key file needs a passphrase. If this

parameter isfalse (the default), then

parameter isoff (the default), then

<varname>ssl_passphrase_command</varname> will be ignored during a

reload and the SSL configuration will not be reloaded if a passphrase

is needed. That setting is appropriate for a command that requires a

TTY for prompting, which might not be available when the server is

running. Setting this parameter totrue might be appropriate if the

running. Setting this parameter toon might be appropriate if the

passphrase is obtained from a file, for example.

</para>

<para>

<listitem>

<para>

Specifies whether to stop just after the specified recovery target

(<literal>true</literal>), or just before the recovery target

(<literal>false</literal>).

(<literal>on</literal>), or just before the recovery target

(<literal>off</literal>).

Applies when <xref linkend="guc-recovery-target-lsn"/>,

<xref linkend="guc-recovery-target-time"/>, or

<xref linkend="guc-recovery-target-xid"/> is specified.

This setting controls whether transactions

having exactly the target WAL location (LSN), commit time, or transaction ID, respectively, will

be included in the recovery. Default is <literal>true</literal>.

be included in the recovery. Default is <literal>on</literal>.

</para>

</listitem>

</varlistentry>

</term>

<listitem>

<para>

Iftrue, any error will terminate the current session. By default,

this is set tofalse, so that only FATAL errors will terminate the

Ifon, any error will terminate the current session. By default,

this is set tooff, so that only FATAL errors will terminate the

session.

</para>

</listitem>

</term>

<listitem>

<para>

When set totrue, which is the default, <productname>PostgreSQL</productname>

When set toon, which is the default, <productname>PostgreSQL</productname>

will automatically reinitialize after a backend crash. Leaving this

value set totrue is normally the best way to maximize the availability

value set toon is normally the best way to maximize the availability

of the database. However, in some circumstances, such as when

<productname>PostgreSQL</productname> is being invoked by clusterware, it may be

useful to disable the restart so that the clusterware can gain

</term>

<listitem>

<para>

When set tofalse, which is the default, <productname>PostgreSQL</productname>

When set tooff, which is the default, <productname>PostgreSQL</productname>

will raise a PANIC-level error on failure to flush modified data files

to the filesystem. This causes the database server to crash.

</para>

faulty hardware.

</para>

<para>

If set totrue, <productname>PostgreSQL</productname> will instead

If set toon, <productname>PostgreSQL</productname> will instead

report an error but continue to run so that the data flushing

operation can be retried in a later checkpoint. Only set it totrue

operation can be retried in a later checkpoint. Only set it toon

after investigating the operating system's treatment of buffered data

in case of write-back failure.

</para>