pgsql: After PageSetAllVisible, use MarkBufferDirty. - Mailing list pgsql-committers

From Robert Haas
Subject pgsql: After PageSetAllVisible, use MarkBufferDirty.
Date
Msg-id E1SKWJF-0000qW-Pi@gemulon.postgresql.org
Whole thread Raw
List pgsql-committers
After PageSetAllVisible, use MarkBufferDirty.

Previously, we used SetBufferCommitInfoNeedsSave, but that's really
intended for dirty-marks we can theoretically afford to lose, such as
hint bits.  As for 9.2, the PD_ALL_VISIBLE mustn't be lost in this
way, since we could then end up with a heap page that isn't
all-visible and a visibility map page that is all visible, causing
index-only scans to return wrong answers.

Branch
------
master

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

Modified Files
--------------
src/backend/commands/vacuumlazy.c |    4 ++--
1 files changed, 2 insertions(+), 2 deletions(-)


pgsql-committers by date:

Previous
From: Robert Haas
Date:
Subject: pgsql: Fix copyfuncs/equalfuncs support for ReassignOwnedStmt.
Next
From: Robert Haas
Date:
Subject: pgsql: Fix incorrect comment in SetBufferCommitInfoNeedsSave().