Skip site navigation (1) Skip section navigation (2)

Re: Dynamic Tracing docs

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: pgsql-hackers(at)postgresql(dot)org, "Simon Riggs" <simon(at)2ndquadrant(dot)com>
Cc: pgsql-patches(at)postgresql(dot)org
Subject: Re: Dynamic Tracing docs
Date: 2006-12-01 23:56:09
Message-ID: 4726.1165017369@sss.pgh.pa.us (view raw or flat)
Thread:
Lists: pgsql-hackerspgsql-patches
"Simon Riggs" <simon(at)2ndquadrant(dot)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

In response to

Responses

pgsql-hackers by date

Next:From: Guillaume LelargeDate: 2006-12-02 00:02:46
Subject: Re: Dynamic Tracing docs
Previous:From: Peter EisentrautDate: 2006-12-01 23:45:37
Subject: Re: [PATCHES] Dynamic Tracing docs

pgsql-patches by date

Next:From: Guillaume LelargeDate: 2006-12-02 00:02:46
Subject: Re: Dynamic Tracing docs
Previous:From: Peter EisentrautDate: 2006-12-01 23:45:37
Subject: Re: [PATCHES] Dynamic Tracing docs

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group