| From: | Alvaro Herrera <alvherre(at)commandprompt(dot)com> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Jakub Ouhrabka <jakub(dot)ouhrabka(at)comgate(dot)cz>, Jakub Ouhrabka <kuba(at)comgate(dot)cz>, Greg Smith <greg(at)2ndquadrant(dot)com>, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: Problem with 8.4 stats collector high load |
| Date: | 2010-02-16 23:12:30 |
| Message-ID: | 20100216231230.GN5330@alvh.no-ip.org |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Tom Lane wrote:
> Alvaro Herrera <alvherre(at)commandprompt(dot)com> writes:
> > Jakub Ouhrabka wrote:
> >> Was autovacuum requesting to write this 20MB file 650x per minute?
>
> > Yes, exactly.
>
> > Ideally, autovacuum would only request a new copy of the file if the one
> > it got was considerably out of date. Obviously a tenth of a second is
> > not old enough.
>
> Wasn't it you that insisted on a short staleness criterion for autovac
> in the first place?
well, my current opinion is that we should spend some nonzero amount of
thought into figuring out what to do.
--
Alvaro Herrera http://www.CommandPrompt.com/
The PostgreSQL Company - Command Prompt, Inc.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Chris Browne | 2010-02-16 23:13:08 | Re: LISTEN/NOTIFY and notification timing guarantees |
| Previous Message | Tom Lane | 2010-02-16 23:05:31 | Re: Problem with 8.4 stats collector high load |