pgsql: Take exclusive buffer lock in scan_heap() to eliminate some

Log Message:
-----------
Take exclusive buffer lock in scan_heap() to eliminate some corner cases
in which invalid page data could be transiently written to disk by
concurrent bgwriter activity. There doesn't seem any risk of loss of
actual user data, but an empty page could possibly be left corrupt if a
crash occurs before the correct data gets written out. Pointed out by
Alvaro Herrera.

Modified Files:
--------------
pgsql/src/backend/commands:
vacuum.c (r1.314 -> r1.315)
(http://developer.postgresql.org/cvsweb.cgi/pgsql/src/backend/commands/vacuum.c.diff?r1=1.314&r2=1.315)
vacuumlazy.c (r1.58 -> r1.59)
(http://developer.postgresql.org/cvsweb.cgi/pgsql/src/backend/commands/vacuumlazy.c.diff?r1=1.58&r2=1.59)