Home
Main website
Display Sidebar
Hide Ads
Recent Changes
View Source:
pg_config(1)
Edit
PageHistory
Diff
Info
LikePages
PG_CONFIG !!!PG_CONFIG NAME SYNOPSIS DESCRIPTION OPTIONS NOTES HISTORY SEE ALSO ---- !!NAME pg_config - retrieve information about the installed version of PostgreSQL !!SYNOPSIS __pg_config__ { __--bindir__ | __--includedir__ | __--includedir-server__ | __--libdir__ | __--pkglibdir__ | __--configure__ | __--version__ }... !!DESCRIPTION The __pg_config__ utility prints configuration parameters of the currently installed version of PostgreSQL. It is intended, for example, to be used by software packages that want to interface to PostgreSQL to facilitate finding the required header files and libraries. !!OPTIONS To use __pg_config__, supply one or more of the following options: __--bindir__ Print the location of user executables. Use this, for example, to find the __psql__ program. This is normally also the location where the ''pg_config'' program resides. __--includedir__ Print the location of C and C++ header files of the client interfaces. __--includedir-server__ Print the location of C and C++ header files for server programming. __--libdir__ Print the location of object code libraries. __--pkglibdir__ Print the location of dynamically loadable modules, or where the server would search for them. (Other architecture-dependent data files may also be installed in this directory.) __--configure__ Print the options that were given to the ''configure'' script when 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.) __--version__ Print the version of PostgreSQL and exit. If more than one option (except for __--version__) is given, the information is printed in that order, one item per line. !!NOTES The option __--includedir-server__ is new in PostgreSQL 7.2. In prior releases, the server include files were installed in the same location as the client headers, which could be queried with the __--includedir__. To make your package handle both cases, try the newer option first and test the exit status to see whether it succeeded. In releases prior to PostgreSQL 7.1, before the __pg_config__ came to be, a method for finding the equivalent configuration information did not exist. !!HISTORY The __pg_config__ utility first appeared in PostgreSQL 7.1. !!SEE ALSO ''PostgreSQL Programmer's Guide'' ----
One page links to
pg_config(1)
:
Man1p
This page is a man page (or other imported legacy content). We are unable to automatically determine the license status of this page.
