Re: autovacuum workers warning - Mailing list pgsql-hackers

From Euler Taveira de Oliveira
Subject Re: autovacuum workers warning
Date
Msg-id 4EA8661E.4060908@timbira.com
Whole thread Raw
In response to Re: autovacuum workers warning  (Alvaro Herrera <alvherre@commandprompt.com>)
Responses Re: autovacuum workers warning  (Alvaro Herrera <alvherre@commandprompt.com>)
Re: autovacuum workers warning  ("Dickson S. Guedes" <listas@guedesoft.net>)
List pgsql-hackers
On 26-10-2011 16:14, Alvaro Herrera wrote:
> Well, just increasing the number of workers would do nothing to solve
> the problem, because the more workers there are, the slower they work.
> The actual solution to the problem would be decreasing
> autovacuum_vacuum_delay_cost, and/or related knobs.
>
Why not? You're saying that parallelizing the work won't help? As about 
autovacuum_vacuum_cost_delay, don't you think that 20ms isn't small enough to 
suggest decreasing instead of increasing the number of workers?

> Wasn't there some discussion recently on measuring the length of the
> work queue, or something like that?
>
Yes, there is. As I said, it is an expensive and approximate measure. I'm not 
saying that is not the right direction, I'm arguing that a hint is better than 
nothing. Right now the only way to know if it is out of workers is to query 
pg_stat_activity frequently.


--    Euler Taveira de Oliveira - Timbira       http://www.timbira.com.br/   PostgreSQL: Consultoria, Desenvolvimento,
Suporte24x7 e Treinamento
 


pgsql-hackers by date:

Previous
From: Chris Redekop
Date:
Subject: Re: Hot Backup with rsync fails at pg_clog if under load
Next
From: Alvaro Herrera
Date:
Subject: Re: autovacuum workers warning