pgsql: Avoid marking buffer dirty when VACUUM has no work to do.

From: Simon Riggs <simon(at)2ndQuadrant(dot)com>
To: pgsql-committers(at)postgresql(dot)org
Subject: pgsql: Avoid marking buffer dirty when VACUUM has no work to do.
Date: 2011-11-18 16:09:57
Message-ID: E1RRR0n-00043Z-0U@gemulon.postgresql.org
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-committers pgsql-hackers

Avoid marking buffer dirty when VACUUM has no work to do.
When wal_level = 'hot_standby' we touched the last page of the
relation during a VACUUM, even if nothing else had happened.
That would alter the LSN of the last block and set the mtime
of the relation file unnecessarily. Noted by Thom Brown.

Branch
------
master

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

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

Responses

Browse pgsql-committers by date

  From Date Subject
Next Message Tom Lane 2011-11-18 16:19:04 Re: pgsql: Avoid marking buffer dirty when VACUUM has no work to do.
Previous Message Tom Lane 2011-11-18 14:54:23 Re: [COMMITTERS] pgsql: Do missed autoheader run for previous commit.

Browse pgsql-hackers by date

  From Date Subject
Next Message David Zwarg 2011-11-18 16:17:13 OidFunctionCall* returning null.
Previous Message Robert Haas 2011-11-18 15:54:40 Re: WIP: Collecting statistics on CSV file data