pgsql: After PageSetAllVisible, use MarkBufferDirty.

From: Robert Haas <rhaas(at)postgresql(dot)org>
To: pgsql-committers(at)postgresql(dot)org
Subject: pgsql: After PageSetAllVisible, use MarkBufferDirty.
Date: 2012-04-18 14:56:41
Message-ID: E1SKWJF-0000qW-Pi@gemulon.postgresql.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: 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(-)

Browse pgsql-committers by date

  From Date Subject
Next Message Andrew Dunstan 2012-04-18 14:58:42 pgsql: Revert recent commit re positional arguments.
Previous Message Robert Haas 2012-04-18 14:47:13 pgsql: Fix copyfuncs/equalfuncs support for ReassignOwnedStmt.