pg.ddx.io  pgsql-admin@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Tom Lane <tgl@sss.pgh.pa.us>
To: Jerry Sievers <jerry@jerrysievers.com>
Cc: pgsql-admin@postgresql.org
Subject: Re: pg_stat_activity showing non-existent processes
Date: Sat, 25 Mar 2006 21:40:08 -0500
Message-ID: <22874.1143340808@sss.pgh.pa.us> (raw)
In-Reply-To: <m3veu2qzh8.fsf@prod01.jerrysievers.com>
References: <m3veu2qzh8.fsf@prod01.jerrysievers.com>

Jerry Sievers <jerry@jerrysievers.com> writes:
> At any rate; I'm wondering what possible causes might be responsible
> for pg_stat_activity's underlying functions to lose track of the valid
> process list?

It sounds like the stats collector missed a few "backend quit"
messages.  This isn't real surprising: the stats messaging mechanism is
intentionally designed to drop messages under severe load, rather than
slow down backends.

We recently put in a filter that prevents reporting pg_stat_activity
lines for backends that are dead according to the up-to-date list in
shared memory.  I don't think that's in 8.0.3 though.

			regards, tom lane



view thread (12+ messages)  latest in thread

Message-ID: <22874.1143340808@sss.pgh.pa.us>
Permalink:  ../22874.1143340808@sss.pgh.pa.us/
Also on:    postgresql.org/message-id/22874.1143340808@sss.pgh.pa.us

 · 

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: tgl@sss.pgh.pa.us, jerry@jerrysievers.com
  Subject: Re: pg_stat_activity showing non-existent processes
  In-Reply-To: <22874.1143340808@sss.pgh.pa.us>
  References: <m3veu2qzh8.fsf@prod01.jerrysievers.com> <22874.1143340808@sss.pgh.pa.us>

* 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