| 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: | 14221.1166680762@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| 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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2006-12-21 06:12:09 | Re: Question about debugging bootstrapping and catalog entries |
| Previous Message | Bruno Wolff III | 2006-12-21 05:40:12 | Re: Release 8.2.0 done, 8.3 development starts |