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

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

From: tgl(at)svr1(dot)postgresql(dot)org (Tom Lane)
To: pgsql-committers(at)postgresql(dot)org
Subject: pgsql: Take exclusive buffer lock in scan_heap() to eliminate some
Date: 2005-09-22 17:32:59
Message-ID: 20050922173259.8E0FCDAA1F@svr1.postgresql.org (view raw or flat)
Thread:
Lists: pgsql-committers
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)

pgsql-committers by date

Next:From: Tom LaneDate: 2005-09-22 18:49:46
Subject: pgsql: Adjust GiST error messages to conform to message style
Previous:From: Bruce MomjianDate: 2005-09-22 16:46:01
Subject: pgsql: This patch cleans up the access to members of ItemIdData.

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