Re: Rethinking stats communication mechanisms - Mailing list pgsql-hackers

From Douglas McNaught
Subject Re: Rethinking stats communication mechanisms
Date
Msg-id 87zmgbuq84.fsf@suzuka.mcnaught.org
Whole thread Raw
In response to Re: Rethinking stats communication mechanisms  (Greg Stark <gsstark@mit.edu>)
Responses Re: Rethinking stats communication mechanisms  (Greg Stark <gsstark@mit.edu>)
List pgsql-hackers
Greg Stark <gsstark@mit.edu> writes:

> PFC <lists@peufeu.com> writes:
>
>>     - Will only be of use if the command is taking a long, long time.
>>     So, it need not be realtime ; no problem if the data comes with a
>> little  delay, or not at all if the command executes quickly.
>
> I would dispute this point. Picture a system running a very short very very
> often. It may still be the main problem, may even be taking 90+% of the cpu
> time. If you got an accurate snapshot of all the currently executing queries
> you'll see it popping up suspiciously often.

Yeah, but if you turn on query logging in that case you'll see the
bajillions of short queries, so you don't need the accurate snapshot
to diagnose that.

-Doug


pgsql-hackers by date:

Previous
From: Greg Stark
Date:
Subject: Re: Rethinking stats communication mechanisms
Next
From: Greg Stark
Date:
Subject: Re: Rethinking stats communication mechanisms