<literal>pl_regression</literal>
   or <literal>contrib_regression</literal>.  Beware of
   using <literal>installcheck</literal> mode with an installation that has
   any non-test databases named that way.
  </para>

  <para>
   Some of these auxiliary test suites use the TAP infrastructure explained
   in <xref linkend="regress-tap"/>.
   The TAP-based tests are run only when PostgreSQL was configured with the
   option <option>--enable-tap-tests</option>.  This is recommended for
   development, but can be omitted if there is no suitable Perl installation.
  </para>

  <para>
   Some test suites are not run by default, either because they are not secure
   to run on a multiuser system, because they require special software or
   because they are resource intensive.  You can decide which test suites to
   run additionally by setting the <command>make</command> or environment
   variable <varname>PG_TEST_EXTRA</varname> to a whitespace-separated list,
   for example:
<programlisting>
make check-world PG_TEST_EXTRA='kerberos ldap ssl load_balance libpq_encryption'
</programlisting>
   The following values are currently supported:
   <variablelist>
    <varlistentry>
     <term><literal>kerberos</literal></term>
     <listitem>
      <para>
       Runs the test suite under <filename>src/test/kerberos</filename>.  This
       requires an MIT Kerberos installation and opens TCP/IP listen sockets.
      </para>
     </listitem>
    </varlistentry>

    <varlistentry>
     <term><literal>ldap</literal></term>
     <listitem>
      <para>
       Runs the test suite under <filename>src/test/ldap</filename>.  This
       requires an <productname>OpenLDAP</productname> installation and opens
       TCP/IP listen sockets.
      </para>
     </listitem>
    </varlistentry>

    <varlistentry>
     <term><literal>sepgsql</literal></term>
     <listitem>
      <para>
       Runs the test suite under <filename>contrib/sepgsql</filename>.  This
       requires an SELinux environment that is set up in a specific way; see
       <xref linkend="sepgsql-regression"/>.
      </para>
     </listitem>
    </varlistentry>

    <varlistentry>
     <term><literal>ssl</literal></term>
     <listitem>
      <para>
       Runs the test suite under <filename>src/test/ssl</filename>.  This opens TCP/IP listen sockets.
      </para>
     </listitem>
    </varlistentry>

    <varlistentry>
     <term><literal>load_balance</literal></term>
     <listitem>
      <para>
       Runs the test <filename>src/interfaces/libpq/t/004_load_balance_dns.pl</filename>.
       This requires editing the system <filename>hosts</filename> file and
       opens TCP/IP listen sockets.
      </para>
     </listitem>
    </varlistentry>

    <varlistentry>
     <term><literal>libpq_encryption</literal></term>
     <listitem>
      <para>
       Runs the test <filename>src/interfaces/libpq/t/005_negotiate_encryption.pl</filename>.
       This opens TCP/IP listen sockets. If <varname>PG_TEST_EXTRA</varname>
       also includes <literal>kerberos</literal>, additional tests that require
       an MIT Kerberos installation are enabled.
      </para>
     </listitem>
    </varlistentry>

    <varlistentry>
     <term><literal>wal_consistency_checking</literal></term>
     <listitem>
      <para>
       Uses <literal>wal_consistency_checking=all</literal> while running
       certain tests under <filename>src/test/recovery</filename>.  Not
       enabled by default because it is resource intensive.
      </para>
     </listitem>
    </varlistentry>

    <varlistentry>
     <term><literal>xid_wraparound</literal></term>
     <listitem>
      <para>
       Runs the test suite under <filename>src/test/modules/xid_wraparound</filename>.
       Not enabled by default because it is resource intensive.
      </para>
     </listitem>
    </varlistentry>

    <varlistentry>
     <term><literal>oauth</literal></term>
     <listitem>
      <para>
       Runs the test suite under <filename>src/test/modules/oauth_validator</filename>.