Re: outdated (bad) information in pg_stat_activity

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: hubert depesz lubaczewski <depesz(at)gmail(dot)com>
Cc: Chris Browne <cbbrowne(at)acm(dot)org>, pgsql-general(at)postgresql(dot)org
Subject: Re: outdated (bad) information in pg_stat_activity
Date: 2005-12-16 03:12:48
Message-ID: 19695.1134702768@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

hubert depesz lubaczewski <depesz(at)gmail(dot)com> writes:
> of course i can make myself a function which will check if pid exists, but
> it would generally be better if there was some way to fix the problem in
> postgresql itself.

Try updating to PG 8.1 ...

2005-08-09 17:14 tgl

* src/backend/postmaster/pgstat.c: Make backends that are reading
the pgstats file verify each backend PID against the PGPROC array.
Anything in the file that isn't in PGPROC gets rejected as being a
stale entry. This should solve complaints about stale entries in
pg_stat_activity after a BETERM message has been dropped due to
overload.

regards, tom lane

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Andrus 2005-12-16 16:16:30 Re: Toolkit for creating editable grid
Previous Message Tom Lane 2005-12-16 00:06:34 Re: Timestamp <-> ctime conversion question ...