I don't want to look a gift horse in the mouth, but it seems to me that the
performance monitor should wait until the now-famous query tree redesign
which will allow for sets from functions. I realize that the shared memory
requirements might be a bit large, but somehow Oracle accomplishes this
nicely, with some > 50 views (V$ACCESS through V$WAITSTAT) which can be
queried, usually via SQL*DBA, for performance statistics. More then 50
performance views may be over-kill, but having the ability to fetch the
performance statistics with normal queries sure is nice. Perhaps a
postmaster option which would enable/disable the use of accumulating
performance statistics in shared memory might ease the hesitation against
it?
Mike Mascari
[EMAIL PROTECTED]
-----Original Message-----
From: Denis Perchine [SMTP:[EMAIL PROTECTED]]
That's bad. Cause it will be unuseful for people having databases far
away...
Like me... :-((( Another point is that it is a little bit strange to have
X-Window on machine with database server... At least if it is not for play,
but production one...
Also there should be a possibility of remote monitoring of the database.
But
that's just dream... :-)))
--
Sincerely Yours,
Denis Perchine
---------------------------(end of broadcast)---------------------------
TIP 4: Don't 'kill -9' the postmaster
