Re: Problem with 8.4 stats collector high load

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Alvaro Herrera <alvherre(at)commandprompt(dot)com>
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:05:31
Message-ID: 18715.1266361531@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:
> 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?

regards, tom lane

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Alvaro Herrera 2010-02-16 23:12:30 Re: Problem with 8.4 stats collector high load
Previous Message David E. Wheeler 2010-02-16 23:04:37 Re: PostgreSQL::PLPerl::Call - Simple interface for calling SQL functions from PostgreSQL PL/Perl