I just noticed that I had accidently responded privately to Roy without
copying to the list.
Below I'm resending my response to his suggestion.
How about this then: a dbms trace point that works like sc906, but logs
ALL
query text along with the start / stop time (a server-wide printqry). If
you
could specify a user_id as filter that would really be cool!
Security auditing already does exactly that. See
http://www.rationalcommerce.com/papers/bench.htm for the recipe to
turn it on and enable the per user filtering. >
Good point, Roy. I was thinking of something more along the lines of a
quick and dirty debugging tool, but if you prepare everything in advance,
you can always turn security auditing off- and on- as needed.
This whole thing came about because I was trying to discover the query text
behind some large prepared queries that are provoking deadlocks and timeouts
at a customer site, without resorting to tracing on each individual client
machine. Security auditing should fit the bill ... it hadn't even ocurred
to me.
Regards,
Jim
_______________________________________________
Users mailing list
[email protected]
http://lists.ingres.com/mailman/listinfo/users
