Re: Rethinking stats communication mechanisms

From: Greg Stark <gsstark(at)mit(dot)edu>
To: PFC <lists(at)peufeu(dot)com>
Cc: "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us>, pgsql-hackers(at)postgresql(dot)org
Subject: Re: Rethinking stats communication mechanisms
Date: 2006-06-18 02:46:04
Message-ID: 87slm35ggj.fsf@stark.xeocode.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers


PFC <lists(at)peufeu(dot)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.

--
greg

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Douglas McNaught 2006-06-18 02:55:55 Re: Rethinking stats communication mechanisms
Previous Message Giampaolo Tomassoni 2006-06-17 23:35:37 R: Per-server univocal identifier