|
1 |
| -<!-- $PostgreSQL: pgsql/doc/src/sgml/ref/pg_config-ref.sgml,v 1.19 2005/01/04 03:58:16 tgl Exp $ --> |
| 1 | +<!-- $PostgreSQL: pgsql/doc/src/sgml/ref/pg_config-ref.sgml,v 1.20 2005/06/09 18:15:05 petere Exp $ --> |
2 | 2 |
|
3 | 3 | <refentry id="app-pgconfig">
|
4 | 4 | <refmeta>
|
|
119 | 119 | This can be used to reproduce the identical configuration, or
|
120 | 120 | to find out with what options a binary package was built. (Note
|
121 | 121 | however that binary packages often contain vendor-specific custom
|
122 |
| - patches.) |
| 122 | + patches.) See also the examples below. |
123 | 123 | </para>
|
124 | 124 | </listitem>
|
125 | 125 | </varlistentry>
|
|
160 | 160 | </refsect1>
|
161 | 161 |
|
162 | 162 |
|
| 163 | + <refsect1> |
| 164 | + <title>Example</title> |
| 165 | + |
| 166 | + <para> |
| 167 | + To reproduce the build configuration of the current PostgreSQL |
| 168 | + installation, run the following command: |
| 169 | +<programlisting> |
| 170 | +eval ./configure `pg_config --configure` |
| 171 | +</programlisting> |
| 172 | + The output of <literal>pg_config --configure</literal> contains |
| 173 | + shell quotation marks so arguments with spaces are represented |
| 174 | + correctly. Therefore, using <literal>eval</literal> is required |
| 175 | + for proper results. |
| 176 | + </para> |
| 177 | + </refsect1> |
| 178 | + |
163 | 179 | <refsect1>
|
164 | 180 | <title>History</title>
|
165 | 181 |
|
|