Skip to content

Undo disarming VM check warning in vacuumlazy.c #213

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Sep 20, 2022
Merged

Undo disarming VM check warning in vacuumlazy.c #213

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Undo diasming VM check warning in vacuumlazy.c
  • Loading branch information
@knizhnik
knizhnik committed Sep 20, 2022
commit ec2f8deadebc024e7858f6c45f95f56c218f66b1
5 changes: 1 addition & 4 deletions src/backend/access/heap/vacuumlazy.c
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -1496,10 +1496,7 @@ lazy_scan_heap(LVRelState *vacrel, VacuumParams *params, bool aggressive)
else if (all_visible_according_to_vm && !PageIsAllVisible(page)
&& VM_ALL_VISIBLE(vacrel->rel, blkno, &vmbuffer))
{
/* ZENITH-XXX: all visible hint is not wal-logged
* FIXME: Replay visibilitymap changes in pageserver
*/
elog(DEBUG1, "page is not marked all-visible but visibility map bit is set in relation \"%s\" page %u",
elog(WARNING, "page is not marked all-visible but visibility map bit is set in relation \"%s\" page %u",
vacrel->relname, blkno);
visibilitymap_clear(vacrel->rel, blkno, vmbuffer,
VISIBILITYMAP_VALID_BITS);
Expand Down