Skip site navigation (1) Skip section navigation (2)

pgsql: Avoid holding vmbuffer pin after VACUUM.

From: Simon Riggs <simon(at)2ndQuadrant(dot)com>
To: pgsql-committers(at)postgresql(dot)org
Subject: pgsql: Avoid holding vmbuffer pin after VACUUM.
Date: 2012-12-03 18:57:54
Message-ID: E1TfbDG-0007a0-TN@gemulon.postgresql.org (view raw or flat)
Thread:
Lists: pgsql-committers
Avoid holding vmbuffer pin after VACUUM.
During VACUUM if we pause to perform a cycle
of index cleanup we drop the vmbuffer pin,
so we should do the same thing when heap
scan completes. This avoids holding vmbuffer
pin across the main index cleanup in VACUUM,
which could be minutes or hours longer than
necessary for correctness.

Bug report and suggested fix from Pavan Deolasee

Branch
------
REL9_2_STABLE

Details
-------
http://git.postgresql.org/pg/commitdiff/17ee02ea1c87b96a4d687d3319f6f4602450d6cb

Modified Files
--------------
src/backend/commands/vacuumlazy.c |   16 +++++++++-------
1 files changed, 9 insertions(+), 7 deletions(-)


pgsql-committers by date

Next:From: Andrew DunstanDate: 2012-12-03 19:28:35
Subject: Re: pgsql: Add mode where contrib installcheck runs each module in a separa
Previous:From: Simon RiggsDate: 2012-12-03 18:54:11
Subject: pgsql: Avoid holding vmbuffer pin after VACUUM.

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group