On Tue, Aug 09, 2005 at 03:19:46PM +0200, Csaba Nagy wrote: > I have a postgres system where we just migrated a fairly big data set. > The application accessing it is a cluster of servers which do burst-like > processing, i.e. when they have some work to do, it will be distributed > in the cluster and the data base will be under fairly high load. > On our first test run everything went fine, the only strange thing is a > row in the pg_stat_activity, which has a row about a query which is long > gone, the process pointed by the procpid field is not existing.
I ran across this situation a while ago, where high load caused pg_stat_activity to have stale entries. Tom Lane wondered if the stats subsystem was under a high enough load that it was dropping messages, as it's designed to do. http://archives.postgresql.org/pgsql-bugs/2004-10/msg00163.php -- Michael Fuhr ---------------------------(end of broadcast)--------------------------- TIP 5: don't forget to increase your free space map settings
