pg.ddx.io  pgsql-admin@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Jim Nasby <jnasby@pervasive.com>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: Kevin Grittner <Kevin.Grittner@wicourts.gov>
Cc: Jerry Sievers <jerry@jerrysievers.com>
Cc: pgsql-admin@postgresql.org
Subject: Re: pg_stat_activity showing non-existent processes
Date: Wed, 5 Apr 2006 18:00:35 -0400
Message-ID: <769B3036-9C41-4DAF-B7A2-EFB603BAE33E@pervasive.com> (raw)
In-Reply-To: <14779.1144083156@sss.pgh.pa.us>
References: <m3veu2qzh8.fsf@prod01.jerrysievers.com>
	<m3veu2qzh8.fsf@prod01.jerrysievers.com>
	<22874.1143340808@sss.pgh.pa.us>
	<443109B6.EE98.0025.0@wicourts.gov>
	<14779.1144083156@sss.pgh.pa.us>

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

> "Kevin Grittner" <Kevin.Grittner@wicourts.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@pervasive.com
Pervasive Software      http://pervasive.com    work: 512-231-6117
vcard: http://jim.nasby.net/pervasive.vcf       cell: 512-569-9461





view thread (12+ messages)

Message-ID: <769B3036-9C41-4DAF-B7A2-EFB603BAE33E@pervasive.com>
Permalink:  ../769B3036-9C41-4DAF-B7A2-EFB603BAE33E@pervasive.com/
Also on:    postgresql.org/message-id/769B3036-9C41-4DAF-B7A2-EFB603BAE33E@pervasive.com

 · 

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients from your mail client; the link fills in
  the headers below: reply via email
  Some clients, webmail especially, drop In-Reply-To and References from
  a link, and the reply then starts a new thread: use the mbox below.

  To: pgsql-admin@postgresql.org
  Cc: jnasby@pervasive.com, tgl@sss.pgh.pa.us, Kevin.Grittner@wicourts.gov, jerry@jerrysievers.com
  Subject: Re: pg_stat_activity showing non-existent processes
  In-Reply-To: <769B3036-9C41-4DAF-B7A2-EFB603BAE33E@pervasive.com>
  References: <m3veu2qzh8.fsf@prod01.jerrysievers.com> <22874.1143340808@sss.pgh.pa.us> <443109B6.EE98.0025.0@wicourts.gov> <14779.1144083156@sss.pgh.pa.us> <769B3036-9C41-4DAF-B7A2-EFB603BAE33E@pervasive.com>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox