<term><option>-Ddocs={ auto | enabled | disabled }</option></term>
<listitem>
<para>
Enables building the documentation in <acronym>HTML</acronym> and
<acronym>man</acronym> format. It defaults to auto.
</para>
</listitem>
</varlistentry>
<varlistentry id="configure-docs-pdf-meson">
<term><option>-Ddocs_pdf={ auto | enabled | disabled }</option></term>
<listitem>
<para>
Enables building the documentation in <acronym>PDF</acronym>
format. It defaults to auto.
</para>
</listitem>
</varlistentry>
<varlistentry id="configure-docs-html-style">
<term><option>-Ddocs_html_style={ simple | website }</option></term>
<listitem>
<para>
Controls which <acronym>CSS</acronym> stylesheet is used. The default
is <literal>simple</literal>. If set to <literal>website</literal>,
the HTML documentation will reference the stylesheet for <ulink
url="https://www.postgresql.org/docs/current/">postgresql.org</ulink>.
</para>
</listitem>
</varlistentry>
</variablelist>
</sect3>
<sect3 id="meson-options-misc">
<title>Miscellaneous</title>
<variablelist>
<varlistentry id="configure-pgport-meson">
<term><option>-Dpgport=<replaceable>NUMBER</replaceable></option></term>
<listitem>
<para>
Set <replaceable>NUMBER</replaceable> as the default port number for
server and clients. The default is 5432. The port can always
be changed later on, but if you specify it here then both
server and clients will have the same default compiled in,
which can be very convenient. Usually the only good reason
to select a non-default value is if you intend to run multiple
<productname>PostgreSQL</productname> servers on the same machine.
</para>
</listitem>
</varlistentry>
<varlistentry id="configure-krb-srvnam-meson">
<term><option>-Dkrb_srvnam=<replaceable>NAME</replaceable></option></term>
<listitem>
<para>
The default name of the Kerberos service principal used
by GSSAPI.
<literal>postgres</literal> is the default. There's usually no
reason to change this unless you are building for a Windows
environment, in which case it must be set to upper case
<literal>POSTGRES</literal>.
</para>
</listitem>
</varlistentry>
<varlistentry id="configure-segsize-meson">
<term><option>-Dsegsize=<replaceable>SEGSIZE</replaceable></option></term>
<listitem>
<para>
Set the <firstterm>segment size</firstterm>, in gigabytes. Large tables are
divided into multiple operating-system files, each of size equal
to the segment size. This avoids problems with file size limits
that exist on many platforms. The default segment size, 1 gigabyte,
is safe on all supported platforms. If your operating system has
<quote>largefile</quote> support (which most do, nowadays), you can use
a larger segment size. This can be helpful to reduce the number of
file descriptors consumed when working with very large tables.
But be careful not to select a value larger than is supported
by your platform and the file systems you intend to use. Other
tools you might wish to use, such as <application>tar</application>, could
also set limits on the usable file size.
It is recommended, though not absolutely required, that this value
be a power of 2.
</para>
</listitem>
</varlistentry>
<varlistentry id="configure-blocksize-meson">
<term><option>-Dblocksize=<replaceable>BLOCKSIZE</replaceable></option></term>
<listitem>
<para>
Set the <firstterm>block size</firstterm>, in kilobytes. This is the unit
of storage and I/O within tables. The default,