Trace Point usage

[ William:
	To set tracepoints (for example in the SQL monitor) to write to a 
	file (you must give the full path) :-


		set trace output '/some/file/or/other'\g
		set trace point XXNNN\g
		...
		...

		set notrace point XXNNN\g
		set notrace output\g

]



From: wiz@telesis.COM (Karl Schendel)

On Sep 5,  7:50, Morey, Robert wrote:
>       Howdy,
>
>       (I hope I don't live to regret this)--the issue was brought up at one of
> the BOFs at IngresWorld.  It appears that a number of (old)long-timers have
> been maintaining their own lists [of trace points].  ...

I think there was a list posted very recently.   That list included
everything I know about, including many trace points that don't
appear to do anything.

The most useful trace points are already generally known.  My personal
list of useful trace points would be:
for tuning and performance info:
  DM420, DM421, QE90, QS501 thru QS505, SC906
  DM1301 thru DM1303, DM1440 are marginally useful

for "doing stuff":
  DM421, DM1305, QS506

for fooling with QEP's:
  OP132, OP133, OP165, OP178, maybe OP182 and OP183

for last-ditch data recovery efforts:
  DM615, DM801, DM802 and may your backup tapes be readable.

there's a whole flock of OPxxx trace points that output "stuff" and
do "stuff", which are all fun to play with.   I don't find any of them really
useful.  The most interesting and understandable is probably OP150,
which should give a flavor of how obscure most of the "stuff" is.

I don't have any experience (yet) trolling for OpenIngres tracepoints.
I would really prefer to see all the neat stuff implemented as IMA
data points, leaving trace points to fulfill what I suppose was their
original function:  implement specific, mysterious data output that
ought to only be useful with the code listing at hand.

-- 
Karl Schendel            Phone: (412) 963-8844
Telesis Computer Corp      Fax: (412) 963-1373
wiz@telesis.com
Ingres Q & A
To William's Home Page
Email William