| 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 |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers pgsql-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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Guillaume Lelarge | 2006-12-02 00:02:46 | Re: Dynamic Tracing docs |
| Previous Message | Peter Eisentraut | 2006-12-01 23:45:37 | Re: [PATCHES] Dynamic Tracing docs |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Guillaume Lelarge | 2006-12-02 00:02:46 | Re: Dynamic Tracing docs |
| Previous Message | Peter Eisentraut | 2006-12-01 23:45:37 | Re: [PATCHES] Dynamic Tracing docs |