|
1 | | -<!-- $PostgreSQL: pgsql/doc/src/sgml/installation.sgml,v 1.319 2009/02/04 21:30:41 alvherre Exp $ --> |
| 1 | +<!-- $PostgreSQL: pgsql/doc/src/sgml/installation.sgml,v 1.320 2009/03/23 01:52:38 tgl Exp $ --> |
2 | 2 |
|
3 | 3 | <chapter id="installation"> |
4 | 4 | <title><![%standalone-include[<productname>PostgreSQL</>]]> |
@@ -1305,31 +1305,32 @@ su - postgres |
1305 | 1305 | <indexterm> |
1306 | 1306 | <primary>DTrace</primary> |
1307 | 1307 | </indexterm> |
1308 | | - Compiles with support for the dynamic tracing tool DTrace. |
1309 | | - Operating system support for DTrace is currently available in |
1310 | | - Solaris and Mac OS X Leopard. |
| 1308 | + Compiles <productname>PostgreSQL</productname> with support for the |
| 1309 | + dynamic tracing tool DTrace. |
| 1310 | + <![%standalone-ignore[See <xref linkend="dynamic-trace"> |
| 1311 | + for more information.]]> |
1311 | 1312 | </para> |
1312 | 1313 |
|
1313 | 1314 | <para> |
1314 | 1315 | To point to the <command>dtrace</command> program, the |
1315 | 1316 | environment variable <envar>DTRACE</envar> can be set. This |
1316 | 1317 | will often be necessary because <command>dtrace</command> is |
1317 | 1318 | typically installed under <filename>/usr/sbin</filename>, |
1318 | | - which might not be in the path. Additional command-line |
1319 | | - options for the <command>dtrace</command> program can be |
1320 | | - specified in the environment variable |
1321 | | - <envar>DTRACEFLAGS</envar>. |
| 1319 | + which might not be in the path. |
1322 | 1320 | </para> |
1323 | 1321 |
|
1324 | 1322 | <para> |
1325 | | - To include DTrace support in a 64-bit binary, specify |
| 1323 | + Extra command-line options for the <command>dtrace</command> program |
| 1324 | + can be specified in the environment variable |
| 1325 | + <envar>DTRACEFLAGS</envar>. On Solaris, |
| 1326 | + to include DTrace support in a 64-bit binary, you must specify |
1326 | 1327 | <literal>DTRACEFLAGS="-64"</> to configure. For example, |
1327 | 1328 | using the GCC compiler: |
1328 | 1329 | <screen> |
1329 | 1330 | ./configure CC='gcc -m64' --enable-dtrace DTRACEFLAGS='-64' ... |
1330 | | -</screen> |
| 1331 | +</screen> |
1331 | 1332 | Using Sun's compiler: |
1332 | | -<screen> |
| 1333 | +<screen> |
1333 | 1334 | ./configure CC='/opt/SUNWspro/bin/cc -xtarget=native64' --enable-dtrace DTRACEFLAGS='-64' ... |
1334 | 1335 | </screen> |
1335 | 1336 | </para> |
@@ -2942,7 +2943,7 @@ LIBOBJS = snprintf.o |
2942 | 2943 | <para> |
2943 | 2944 | Yes, using DTrace is possible. See <![%standalone-include[the |
2944 | 2945 | documentation]]> |
2945 | | - <![%standalone-ignore[<xref linkend="monitoring">]]> for further |
| 2946 | + <![%standalone-ignore[<xref linkend="dynamic-trace">]]> for further |
2946 | 2947 | information. You can also find more information in this |
2947 | 2948 | article: <ulink url="http://blogs.sun.com/robertlor/entry/user_level_dtrace_probes_in"></ulink>. |
2948 | 2949 | </para> |
|