Re: Performance monitor

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>
Cc: The Hermit Hacker <scrappy(at)hub(dot)org>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Performance monitor
Date: 2001-03-07 22:30:08
Message-ID: 14289.984004208@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> writes:
> How do people feel about adding a single handler to 7.1? Is it
> something I can slip into the current CVS, or will it have to exist as a
> patch to 7.1. Seems it would be pretty isolated unless someone sends
> the signal, but it is clearly a feature addition.

> OK, I will distribute it as a patch.

Patch or otherwise, this approach seems totally unworkable. A signal
handler cannot do I/O safely, it cannot look at shared memory safely,
it cannot even look at the backend's own internal state safely. How's
it going to do any useful status reporting?

Firing up a separate backend process that looks at shared memory seems
like a more useful design in the long run. That will mean exporting
more per-backend status into shared memory, however, and that means that
this is not a trivial change.

regards, tom lane

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Bruce Momjian 2001-03-07 22:42:05 Re: Performance monitor
Previous Message Tom Lane 2001-03-07 22:15:59 Re: AW: Proposed WAL changes