From: | Alfred Perlstein <bright(at)wintelcom(dot)net> |
---|---|
To: | Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> |
Cc: | PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: Performance monitor signal handler |
Date: | 2001-03-12 21:34:00 |
Message-ID: | 20010312133359.Z18351@fw.wintelcom.net |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
* Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> [010312 12:12] wrote:
> I was going to implement the signal handler like we do with Cancel,
> where the signal sets a flag and we check the status of the flag in
> various _safe_ places.
>
> Can anyone think of a better way to get information out of a backend?
Why not use a static area of the shared memory segment? Is it possible
to have a spinlock over it so that an external utility can take a snapshot
of it with the spinlock held?
Also, this could work for other stuff as well, instead of overloading
a lot of signal handlers one could just periodically poll a region of
the shared segment.
just some ideas..
--
-Alfred Perlstein - [bright(at)wintelcom(dot)net|alfred(at)freebsd(dot)org]
Daemon News Magazine in your snail-mail! http://magazine.daemonnews.org/
From | Date | Subject | |
---|---|---|---|
Next Message | Nathan Myers | 2001-03-12 21:38:09 | Re: Banner links not working (fwd) |
Previous Message | Ralf Edmund Stranzenbach | 2001-03-12 21:12:58 | JDBC handling of a Timestamp-Column |