Re: Performance monitor signal handler - Mailing list pgsql-hackers

From Bruce Momjian
Subject Re: Performance monitor signal handler
Date
Msg-id 200103131503.KAA10241@candle.pha.pa.us
Whole thread Raw
In response to Performance monitor signal handler  (Bruce Momjian <pgman@candle.pha.pa.us>)
Responses Re: Performance monitor signal handler  (Jan Wieck <janwieck@Yahoo.com>)
List pgsql-hackers
> > I think Tom has previously stated that there are technical reasons not to
> > do IO in signal handlers, and I have philosophical problems with
> > performance monitors that ask 50 backends to do file IO. I really do think
> > shared memory is TWTG.
> 
> I wasn't really suggesting any of those courses of action, all I
> suggested was using rename(2) to give a seperate appilcation a
> consistant snapshot of the stats.
> 
> Actually, what makes the most sense (although it may be a performance
> killer) is to have the backends update a system table that the external
> app can query.

Yes, it seems storing info in shared memory and having a system table to
access it is the way to go.

--  Bruce Momjian                        |  http://candle.pha.pa.us pgman@candle.pha.pa.us               |  (610)
853-3000+  If your life is a hard drive,     |  830 Blythe Avenue +  Christ can be your backup.        |  Drexel Hill,
Pennsylvania19026
 


pgsql-hackers by date:

Previous
From: Alfred Perlstein
Date:
Subject: Re: Performance monitor signal handler
Next
From: Thomas Graichen
Date:
Subject: Re: PostgreSQL on multi-CPU systems