[EMAIL PROTECTED] (Tom Lane) writes: > Chris Browne <[EMAIL PROTECTED]> 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.)
That seems a *bit* surprising; the system wasn't expected to be under particularly heavy load during the period in question; I would have expected "particularly light load." No matter; there may have been some brief heavy load to cause this. There isn't any way, short of restarting the postmaster, to get rid of that PID, is there? -- "cbbrowne","@","linuxdatabases.info" http://cbbrowne.com/info/linuxdistributions.html "High-level languages are a pretty good indicator that all else is seldom equal." - Tim Bradshaw, comp.lang.lisp ---------------------------(end of broadcast)--------------------------- TIP 1: if posting/reading through Usenet, please send an appropriate subscribe-nomail command to [EMAIL PROTECTED] so that your message can get through to the mailing list cleanly
