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

From hubert depesz lubaczewski
Subject Re: outdated (bad) information in pg_stat_activity
Date
Msg-id 9e4684ce0512170313v17b564a2qca76be96bf3cdf13@mail.gmail.com
Whole thread Raw
In response to Re: outdated (bad) information in pg_stat_activity  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: outdated (bad) information in pg_stat_activity
List pgsql-general
On 12/16/05, Tom Lane <tgl@sss.pgh.pa.us> wrote:
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.

must have missed that one. thanks - we are moving to 8.1 anyway (50-150% increase in performance for some specific tasks!).

depesz

pgsql-general by date:

Previous
From: Karsten Hilbert
Date:
Subject: Re: is this a bug or I am blind?
Next
From: Andre Truter
Date:
Subject: DBlink documentation