pgsql: Fix leakage of cost_limit when multiple autovacuum workers are a

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: pgsql-committers(at)postgresql(dot)org
Subject: pgsql: Fix leakage of cost_limit when multiple autovacuum workers are a
Date: 2010-11-20 03:30:00
Message-ID: E1PJe9I-0001uM-Us@gemulon.postgresql.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-committers

Fix leakage of cost_limit when multiple autovacuum workers are active.

When using default autovacuum_vac_cost_limit, autovac_balance_cost relied
on VacuumCostLimit to contain the correct global value ... but after the
first time through in a particular worker process, it didn't, because we'd
trashed it in previous iterations. Depending on the state of other autovac
workers, this could result in a steady reduction of the effective
cost_limit setting as a particular worker processed more and more tables,
causing it to go slower and slower. Spotted by Simon Poole (bug #5759).
Fix by saving and restoring the GUC variables in the loop in do_autovacuum.

In passing, improve a few comments.

Back-patch to 8.3 ... the cost rebalancing code has been buggy since it was
put in.

Branch
------
master

Details
-------
http://git.postgresql.org/gitweb?p=postgresql.git;a=commitdiff;h=b58c25055ef6d7097618c680f6768689a110d529

Modified Files
--------------
src/backend/postmaster/autovacuum.c | 63 +++++++++++++++++++++++++----------
1 files changed, 45 insertions(+), 18 deletions(-)

Browse pgsql-committers by date

  From Date Subject
Next Message Tom Lane 2010-11-20 03:30:01 pgsql: Fix leakage of cost_limit when multiple autovacuum workers are a
Previous Message Robert Haas 2010-11-20 03:15:41 pgsql: Speed up conversion of signed integers to C strings.