| From: | Mark Kirkwood <mark(dot)kirkwood(at)catalyst(dot)net(dot)nz> |
|---|---|
| To: | Amit Kapila <amit(dot)kapila16(at)gmail(dot)com>, Haribabu Kommi <kommi(dot)haribabu(at)gmail(dot)com> |
| Cc: | Alvaro Herrera <alvherre(at)2ndquadrant(dot)com>, "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Per table autovacuum vacuum cost limit behaviour strange |
| Date: | 2014-05-05 06:27:47 |
| Message-ID: | 53672F63.3080400@catalyst.net.nz |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 05/05/14 15:22, Amit Kapila wrote:
> Here what I could understand is that sum of cost_limit for all
> autovacuum workers should never exceed the value of
> autovacuum_vacuum_cost_limit which seems to be always the
> case in current code but same is not true for proposed patch.
>
Right, but have a look at the 1st message in this thread - the current
behavior (and to a large extent the above condition) means that setting
cost limits per table does not work in any remotely intuitive way.
ITSM that the whole purpose of a per table setting in this context is to
override the behavior of auto vacuum throttling - and currently this
does not happen unless you get real brutal (i.e setting the cost delay
to zero in addition to setting cost limit...making the whole cost limit
a bit pointless).
regards
Mark
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Heikki Linnakangas | 2014-05-05 06:40:59 | Re: Sending out a request for more buildfarm animals? |
| Previous Message | Heikki Linnakangas | 2014-05-05 06:23:15 | Re: 9.4 release notes |