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

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: (view raw, whole thread or download thread mbox)
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.



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

pgsql-committers by date

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

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