2000-08-26 15:08:16 +02:00
|
|
|
<!-- $Header -->
|
|
|
|
|
2000-10-11 00:03:31 +02:00
|
|
|
<refentry id="app-pg_config">
|
2000-08-26 15:08:16 +02:00
|
|
|
<refmeta>
|
2000-10-11 00:03:31 +02:00
|
|
|
<refentrytitle id="app-pg_config-title">pg_config</>
|
2000-08-26 15:08:16 +02:00
|
|
|
<refmiscinfo>Application</>
|
|
|
|
</refmeta>
|
|
|
|
|
|
|
|
<refnamediv>
|
2000-10-11 00:03:31 +02:00
|
|
|
<refname>pg_config</>
|
2000-08-26 15:08:16 +02:00
|
|
|
<refpurpose>Provides information about the installed version of <productname>PostgreSQL</></>
|
|
|
|
</refnamediv>
|
|
|
|
|
|
|
|
<refsynopsisdiv>
|
|
|
|
<synopsis>
|
2000-10-11 00:03:31 +02:00
|
|
|
pg_config --bindir | --includedir | --libdir | --configure | --version
|
2000-08-26 15:08:16 +02:00
|
|
|
</synopsis>
|
|
|
|
</refsynopsisdiv>
|
|
|
|
|
|
|
|
<refsect1>
|
|
|
|
<title>Description</>
|
|
|
|
<para>
|
2000-10-11 00:03:31 +02:00
|
|
|
The <application>pg_config</> stores and provides configuration parameters
|
2000-08-26 15:08:16 +02:00
|
|
|
of the currently installed version of <productname>PostgreSQL</>. It is
|
|
|
|
intended, for example, to be used by software packages that want to interface
|
|
|
|
to <productname>PostgreSQL</> in order to find the respective header files
|
|
|
|
and libraries.
|
|
|
|
</para>
|
|
|
|
|
|
|
|
<para>
|
2000-10-11 00:03:31 +02:00
|
|
|
To use <application>pg_config</>, supply one or more of the following options:
|
2000-08-26 15:08:16 +02:00
|
|
|
<variablelist>
|
|
|
|
<varlistentry>
|
|
|
|
<term>--bindir</>
|
|
|
|
<listitem>
|
|
|
|
<para>
|
|
|
|
Print the location of user executables. Use this, for example, to find
|
|
|
|
the <application>psql</> program. This is normally also the location
|
2000-10-11 00:03:31 +02:00
|
|
|
where the <filename>pg_config</> program resides.
|
2000-08-26 15:08:16 +02:00
|
|
|
</para>
|
|
|
|
</listitem>
|
|
|
|
</varlistentry>
|
|
|
|
|
|
|
|
<varlistentry>
|
|
|
|
<term>--includedir</>
|
|
|
|
<listitem>
|
|
|
|
<para>
|
|
|
|
Print the location of C and C++ header files.
|
|
|
|
</para>
|
|
|
|
</listitem>
|
|
|
|
</varlistentry>
|
|
|
|
|
|
|
|
<varlistentry>
|
|
|
|
<term>--libdir</>
|
|
|
|
<listitem>
|
|
|
|
<para>
|
|
|
|
Print the location of object code libraries.
|
|
|
|
</para>
|
|
|
|
</listitem>
|
|
|
|
</varlistentry>
|
|
|
|
|
|
|
|
<varlistentry>
|
|
|
|
<term>--configure</>
|
|
|
|
<listitem>
|
|
|
|
<para>
|
|
|
|
Print the options that were given to the <filename>configure</>
|
|
|
|
script when <productname>PostgreSQL</> was configured for building.
|
|
|
|
This can be used to reproduce the identical configuration, or
|
|
|
|
to find out with what options a binary package was built. (Note
|
|
|
|
however that binary packages often contain vendor-specific custom
|
|
|
|
patches.)
|
|
|
|
</para>
|
|
|
|
</listitem>
|
|
|
|
</varlistentry>
|
|
|
|
|
|
|
|
<varlistentry>
|
|
|
|
<term>--version</>
|
|
|
|
<listitem>
|
|
|
|
<para>
|
|
|
|
Print the version of <productname>PostgreSQL</> and exit.
|
|
|
|
</para>
|
|
|
|
</listitem>
|
|
|
|
</varlistentry>
|
|
|
|
</variablelist>
|
|
|
|
|
|
|
|
If more than one option (except for <option>--version</>) is given, the
|
|
|
|
information is printed in that order, one item per line.
|
|
|
|
</para>
|
|
|
|
</refsect1>
|
|
|
|
</refentry>
|