pgsql: Avoid holding vmbuffer pin after VACUUM. - Mailing list pgsql-committers

From Simon Riggs
Subject pgsql: Avoid holding vmbuffer pin after VACUUM.
Date
Msg-id E1TfbDG-0007a4-Tf@gemulon.postgresql.org
Whole thread Raw
List 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_0_STABLE

Details
-------
http://git.postgresql.org/pg/commitdiff/c52e0e2afc0c8ca2de4e03fc8478d89b4d5e7fce

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


pgsql-committers by date:

Previous
From: Simon Riggs
Date:
Subject: pgsql: Avoid holding vmbuffer pin after VACUUM.
Next
From: Andrew Dunstan
Date:
Subject: Re: pgsql: Add mode where contrib installcheck runs each module in a separa