Re: Performance monitor
Richard Kuhns <rjk@grauel.com>
From: Richard J Kuhns <rjk@grauel.com>
To: Bruce Momjian <pgman@candle.pha.pa.us>
Cc: Tom Lane <tgl@sss.pgh.pa.us>, Karel Zak <zakkr@zf.jcu.cz>, Philip Warner <pjw@rhyme.com.au>, Justin Clift <aa2@bigpond.net.au>, The Hermit Hacker <scrappy@hub.org>, PostgreSQL-development <pgsql-hackers@postgresql.org>
Date: 2001-03-08T18:44:05Z
Lists: pgsql-hackers
Bruce Momjian writes: ... > The problem I see with the shared memory idea is that some of the > information needed may be quite large. For example, query strings can > be very long. Do we just allocate 512 bytes and clip off the rest. And > as I add more info, I need more shared memory per backend. I just liked > the file system dump solution because I could modify it pretty easily, > and because the info only appears when you click on the process, it > doesn't happen often. > Have you thought about using a named pipe? They've been around for quite a while, and should (he said with a :-)) be available on most-if-not-all currently supported systems. -- Richard Kuhns rjk@grauel.com PO Box 6249 Tel: (765)477-6000 \ 100 Sawmill Road x319 Lafayette, IN 47903 (800)489-4891 /