| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Jan Wieck <JanWieck(at)Yahoo(dot)com> |
| Cc: | Csaba Nagy <nagy(at)ecircle-ag(dot)com>, Postgres general mailing list <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: Query stucked in pg_stat_activity |
| Date: | 2005-08-09 16:53:19 |
| Message-ID: | 17110.1123606399@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
Jan Wieck <JanWieck(at)Yahoo(dot)com> writes:
>> Jan, any thoughts?
> The reset call is supposed to throw away everything. If it leaves crap
> behind, I'd call that a bug.
resetcounters only thinks it is supposed to zero the counters for the
current database. That seems considerably different from "throw away
everything". In any case, with autovacuum coming up fast on the outside
it doesn't seem that we want to encourage people to reset the stats on
a routine basis.
> IIRC the pg_stat functions don't examine the shared memory, but rely
> entirely on information from the stats file. It sure would be possible
> to add something there that checks the PGPROC array.
Yeah. I'll take a look at doing this.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Joel Fradkin | 2005-08-09 16:56:37 | Re: [GENERAL] postgres & server encodings |
| Previous Message | Lincoln Yeoh | 2005-08-09 16:52:00 | Re: postgres & server encodings |