Re: outdated (bad) information in pg_stat_activity - Mailing list pgsql-general

From Tom Lane
Subject Re: outdated (bad) information in pg_stat_activity
Date
Msg-id 19695.1134702768@sss.pgh.pa.us
Whole thread Raw
In response to Re: outdated (bad) information in pg_stat_activity  (hubert depesz lubaczewski <depesz@gmail.com>)
Responses Re: outdated (bad) information in pg_stat_activity
List pgsql-general
hubert depesz lubaczewski <depesz@gmail.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

pgsql-general by date:

Previous
From: hubert depesz lubaczewski
Date:
Subject: Re: outdated (bad) information in pg_stat_activity
Next
From: "dfx"
Date:
Subject: Migration tool from MS SQL server 7.0