Skip site navigation (1) Skip section navigation (2)

Re: Stats Collector Oddity

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Chris Browne <cbbrowne(at)acm(dot)org>
Cc: pgsql-hackers(at)postgresql(dot)org
Subject: Re: Stats Collector Oddity
Date: 2006-12-21 05:59:22
Message-ID: (view raw or whole thread)
Lists: pgsql-hackers
Chris Browne <cbbrowne(at)acm(dot)org> writes:
> We're getting a bit of an anomaly relating to pg_stat_activity...
> ...
> That PID has been dead for several days, but this connection is marked
> as being open, still, after lo many days.

This probably just means that the "backend termination" stats message
got dropped due to heavy load.  That's expected behavior in all pre-8.2
releases: the stats system was never intended to provide
guaranteed-exactly-correct status.  PG 8.2 has reimplemented the
pg_stat_activity view to make it more trustworthy.  (The other stuff is
still probabilistic, but being just event counters, message loss isn't
so obvious.)

			regards, tom lane

In response to


pgsql-hackers by date

Next:From: Tom LaneDate: 2006-12-21 06:12:09
Subject: Re: Question about debugging bootstrapping and catalog entries
Previous:From: Bruno Wolff IIIDate: 2006-12-21 05:40:12
Subject: Re: Release 8.2.0 done, 8.3 development starts

Privacy Policy | About PostgreSQL
Copyright © 1996-2015 The PostgreSQL Global Development Group