Re: [PATCHES] Dynamic Tracing docs - Mailing list pgsql-hackers

From Tom Lane
Subject Re: [PATCHES] Dynamic Tracing docs
Date
Msg-id 4726.1165017369@sss.pgh.pa.us
Whole thread Raw
Responses Re: [PATCHES] Dynamic Tracing docs  (Theo Schlossnagle <jesus@omniti.com>)
Re: [PATCHES] Dynamic Tracing docs  ("Simon Riggs" <simon@2ndquadrant.com>)
Re: [PATCHES] Dynamic Tracing docs  (Bruce Momjian <bruce@momjian.us>)
List pgsql-hackers
"Simon Riggs" <simon@2ndquadrant.com> writes:
> This includes refactoring of some of the trace related GUC docs from
> config.sgml, so its all in the one place.

Why exactly is that a good idea?  Since DTrace is Solaris-only, this
almost seems like an attempt to hide non-Solaris-specific information
where people won't look for it.  Moreover, the point of config.sgml
is to describe all the configuration parameters in one place.  We do not
need to have people second-guessing that decision for random subsets
of the parameters.

            regards, tom lane

pgsql-hackers by date:

Previous
From: "Simon Riggs"
Date:
Subject: Re: FOR SHARE vs FOR UPDATE locks
Next
From: Theo Schlossnagle
Date:
Subject: Re: [PATCHES] Dynamic Tracing docs