Penguin
Recent Changes
Blame: pg_config(1)
EditPageHistoryDiffInfoLikePages
Annotated edit history of pg_config(1) version 1, including all changes. View license author blame.
Rev Author # Line
1 perry 1 PG_CONFIG
2 !!!PG_CONFIG
3 NAME
4 SYNOPSIS
5 DESCRIPTION
6 OPTIONS
7 NOTES
8 HISTORY
9 SEE ALSO
10 ----
11 !!NAME
12
13
14 pg_config - retrieve information about the installed version of PostgreSQL
15 !!SYNOPSIS
16
17
18 __pg_config__ { __--bindir__ | __--includedir__ |
19 __--includedir-server__ | __--libdir__ |
20 __--pkglibdir__ | __--configure__ | __--version__
21 }...
22 !!DESCRIPTION
23
24
25 The __pg_config__ utility prints configuration parameters
26 of the currently installed version of PostgreSQL. It is
27 intended, for example, to be used by software packages that
28 want to interface to PostgreSQL to facilitate finding the
29 required header files and libraries.
30 !!OPTIONS
31
32
33 To use __pg_config__, supply one or more of the following
34 options:
35
36
37 __--bindir__
38
39
40 Print the location of user executables. Use this, for
41 example, to find the __psql__ program. This is normally
42 also the location where the ''pg_config'' program
43 resides.
44
45
46 __--includedir__
47
48
49 Print the location of C and C++ header files of the client
50 interfaces.
51
52
53 __--includedir-server__
54
55
56 Print the location of C and C++ header files for server
57 programming.
58
59
60 __--libdir__
61
62
63 Print the location of object code libraries.
64
65
66 __--pkglibdir__
67
68
69 Print the location of dynamically loadable modules, or where
70 the server would search for them. (Other
71 architecture-dependent data files may also be installed in
72 this directory.)
73
74
75 __--configure__
76
77
78 Print the options that were given to the ''configure''
79 script when PostgreSQL was configured for building. This can
80 be used to reproduce the identical configuration, or to find
81 out with what options a binary package was built. (Note
82 however that binary packages often contain vendor-specific
83 custom patches.)
84
85
86 __--version__
87
88
89 Print the version of PostgreSQL and exit.
90
91
92 If more than one option (except for __--version__) is
93 given, the information is printed in that order, one item
94 per line.
95 !!NOTES
96
97
98 The option __--includedir-server__ is new in PostgreSQL
99 7.2. In prior releases, the server include files were
100 installed in the same location as the client headers, which
101 could be queried with the __--includedir__. To make your
102 package handle both cases, try the newer option first and
103 test the exit status to see whether it
104 succeeded.
105
106
107 In releases prior to PostgreSQL 7.1, before the
108 __pg_config__ came to be, a method for finding the
109 equivalent configuration information did not
110 exist.
111 !!HISTORY
112
113
114 The __pg_config__ utility first appeared in PostgreSQL
115 7.1.
116 !!SEE ALSO
117
118
119 ''PostgreSQL Programmer's Guide''
120 ----
This page is a man page (or other imported legacy content). We are unable to automatically determine the license status of this page.