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

pgsql: Continue to allow VACUUM to mark last block of index dirty

From: Simon Riggs <simon(at)2ndQuadrant(dot)com>
To: pgsql-committers(at)postgresql(dot)org
Subject: pgsql: Continue to allow VACUUM to mark last block of index dirty
Date: 2011-11-22 09:48:54
Message-ID: E1RSmyE-00061D-1F@gemulon.postgresql.org (view raw or flat)
Thread:
Lists: pgsql-committers
Continue to allow VACUUM to mark last block of index dirty
even when there is no work to do. Further analysis required.
Revert of patch c1458cc495ff800cd176a1c2e56d8b62680d9b71

Branch
------
master

Details
-------
http://git.postgresql.org/pg/commitdiff/2d2841a56c8fa37a5dd5c6d33488ba6ca37116ff

Modified Files
--------------
src/backend/access/nbtree/nbtpage.c |   12 ++++--------
1 files changed, 4 insertions(+), 8 deletions(-)

pgsql-committers by date

Next:From: Peter EisentrautDate: 2011-11-22 19:15:58
Subject: pgsql: Small markup and wording improvement
Previous:From: Simon RiggsDate: 2011-11-22 09:36:52
Subject: Re: [COMMITTERS] pgsql: Avoid marking buffer dirty when VACUUM has no work to do.

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