pgsql: Avoid marking buffer dirty when VACUUM has no work to do. - Mailing list pgsql-committers

From Simon Riggs
Subject pgsql: Avoid marking buffer dirty when VACUUM has no work to do.
Date
Msg-id E1RRR0n-00043Z-0U@gemulon.postgresql.org
Whole thread Raw
Responses Re: pgsql: Avoid marking buffer dirty when VACUUM has no work to do.  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-committers
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(-)


pgsql-committers by date:

Previous
From: Alvaro Herrera
Date:
Subject: Re: pgsql: Do missed autoheader run for previous commit.
Next
From: Tom Lane
Date:
Subject: Re: pgsql: Avoid marking buffer dirty when VACUUM has no work to do.