Hi,
Some time ago [1], I proposed print a message every time there isn't
autovacuum slots available and it asks for another one. It is not a complete
solution for autovacuum tuning but it would at least give us a hint that
number of workers is insufficient to keep up with the current load.
Euler Taveira de Oliveira eu...@timbira.com writes:
+ if (!can_launch)
+ ereport(LOG,
+ (errmsg(maximum number of autovacuum
workers reached),
+ errhint(Consider increasing
Excerpts from Euler Taveira de Oliveira's message of mar oct 25 16:56:12 -0300
2011:
Hi,
Some time ago [1], I proposed print a message every time there isn't
autovacuum slots available and it asks for another one. It is not a complete
solution for autovacuum tuning but it would at least
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
Excerpts from Euler Taveira de Oliveira's message of mié oct 26 16:57:18 -0300
2011:
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
2011/10/26 Euler Taveira de Oliveira eu...@timbira.com:
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.
The currently number of autovaccum workers
