Re: outdated (bad) information in pg_stat_activity

From: Chris Browne <cbbrowne(at)acm(dot)org>
To: pgsql-general(at)postgresql(dot)org
Subject: Re: outdated (bad) information in pg_stat_activity
Date: 2005-12-14 19:06:57
Message-ID: 60mzj3pkfi.fsf@dba2.int.libertyrms.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

depesz(at)gmail(dot)com (hubert depesz lubaczewski) writes:
> On 12/14/05, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
>
>
> hubert depesz lubaczewski <depesz(at)gmail(dot)com> writes:
> > my pg_stat_activity is raporting process working on a query for 12 hours
> > straight! (query_start).
> > 2 problems:
> > 1. this particular query runs typically between 80 and 200 miliseconds!
> > 2. procpid of this backend does not exists anymore in system
> It's possible that the "backend exited" message got dropped by the stats
> mechanism --- the stats code is deliberately designed to lose messages
> rather than delay the rest of the system, so it's not 100% reliable.
>
>
>
> is it possible to "by hand" remove bad entries from this stats?
> depesz

The only answer I have been able to come to is that restarting the
postmaster will clear this all up.

If there is some less intrusive way of accomplishing this, I'd be keen
on hearing about it...
--
"cbbrowne","@","cbbrowne.com"
http://cbbrowne.com/info/nonrdbms.html
"Funny, the only thing that makes me go Keanu about Microsoft is the
fact that they are constantly behind the times and yet claim to be
innovating." -- Steve Lamb <morpheus(at)despair(dot)rpglink(dot)com>

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Terry Lee Tucker 2005-12-14 19:11:23 Re: to_char() Question
Previous Message Bruno Wolff III 2005-12-14 18:09:38 Re: to_char() Question