| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Alvaro Herrera <alvherre(at)commandprompt(dot)com> |
| Cc: | Andrew Dunstan <andrew(at)dunslane(dot)net>, Stefan Kaltenbrunner <stefan(at)kaltenbrunner(dot)cc>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Status of autovacuum and the sporadic stats failures ? |
| Date: | 2007-02-07 19:30:30 |
| Message-ID: | 20818.1170876630@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Alvaro Herrera <alvherre(at)commandprompt(dot)com> writes:
> Tom Lane wrote:
>> We could make it cleaner by inventing a function to clear out the cached
>> statistics within a transaction, perhaps "pg_stat_reset_snaphot()" or
>> some such name. If anyone thinks that that would be of general
>> usefulness, I'll see about making it happen.
> I came up with the idea of storing the stat hash in a particular memory
> context, and have a flag in pgstat.c that's reset when that context is
> reset. So each caller can define what's the appropriate lifetime.
None of your use-cases require tracking multiple sets of stats within a
transaction, so I don't see why bother with that when we can just add a
"flush the stats" call.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Bruce Momjian | 2007-02-07 19:34:35 | Subject supressed |
| Previous Message | Bruno Wolff III | 2007-02-07 19:23:20 | Re: Chatter on DROP SOMETHING IF EXISTS |