Location via proxy:   [ UP ]  
[Report a bug]   [Manage cookies]                
Skip to content

Commit 65d2732

Browse files
committed
Add example for pg_config --configure.
1 parent ebc8649 commit 65d2732

File tree

1 file changed

+18
-2
lines changed

1 file changed

+18
-2
lines changed

doc/src/sgml/ref/pg_config-ref.sgml

Lines changed: 18 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -1,4 +1,4 @@
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 $ -->
22

33
<refentry id="app-pgconfig">
44
<refmeta>
@@ -119,7 +119,7 @@
119119
This can be used to reproduce the identical configuration, or
120120
to find out with what options a binary package was built. (Note
121121
however that binary packages often contain vendor-specific custom
122-
patches.)
122+
patches.) See also the examples below.
123123
</para>
124124
</listitem>
125125
</varlistentry>
@@ -160,6 +160,22 @@
160160
</refsect1>
161161

162162

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+
163179
<refsect1>
164180
<title>History</title>
165181

0 commit comments

Comments
 (0)