Re: pg_stat_activity showing non-existent processes

From: Jim Nasby <jnasby(at)pervasive(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: "Kevin Grittner" <Kevin(dot)Grittner(at)wicourts(dot)gov>, "Jerry Sievers" <jerry(at)jerrysievers(dot)com>, pgsql-admin(at)postgresql(dot)org
Subject: Re: pg_stat_activity showing non-existent processes
Date: 2006-04-05 22:00:35
Message-ID: 769B3036-9C41-4DAF-B7A2-EFB603BAE33E@pervasive.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-admin

On Apr 3, 2006, at 12:52 PM, Tom Lane wrote:

> "Kevin Grittner" <Kevin(dot)Grittner(at)wicourts(dot)gov> writes:
>> Is there any way to tweak this in favor of more accurate information,
>> even if has a performance cost? We're finding that during normal
>> operations we're not seeing most connections added to the
>> pg_stat_activity table. We would like to be able to count on
>> accurate
>> information there.
>
> That's basically a non-starter because of the delay in reporting from
> the stats collector process (ie, even if the information was
> "completely
> accurate" it'd still be stale by the time that your code gets its
> hands
> on it). I think you'd be talking about a complete redesign of the
> stats
> subsystem to be able to use it that way.

BTW, there's some effort going into adding monitoring probes such as
dtrace to PostgreSQL. These would likely be ideal for what you're
trying to do.
--
Jim C. Nasby, Sr. Engineering Consultant jnasby(at)pervasive(dot)com
Pervasive Software http://pervasive.com work: 512-231-6117
vcard: http://jim.nasby.net/pervasive.vcf cell: 512-569-9461

In response to

Browse pgsql-admin by date

  From Date Subject
Next Message Tomeh, Husam 2006-04-05 22:42:08 Re: Error Handling with COPY command
Previous Message Jim Nasby 2006-04-05 21:59:40 Re: pg_stat_activity showing non-existent processes