Crash safe visibility map vs hint bits - Mailing list pgsql-hackers

From Jesper@Krogh.cc
Subject Crash safe visibility map vs hint bits
Date
Msg-id 41D1FA6A-4C19-4266-833F-9AF585ECD70C@krogh.cc
Whole thread Raw
Responses Re: Crash safe visibility map vs hint bits  (Heikki Linnakangas <heikki.linnakangas@enterprisedb.com>)
List pgsql-hackers
There has been a lot discussion about index-only scans and how to make the visibillity map crash safe. Then followed by
agood discussion about hint bits. 

What seems to be the main concern is the added wal volume and it makes me wonder if there is a way in-between that
looksmore like hint bits. 

How about lazily wal-log the complete visibility map say every X minutes or N amount of tuple updates and make the wal
recoveryjobs of rechecking visibility of pages touched by the wal stream on recovery. 

This seems a lot like the checkpoint mechanism but I can't see if it can just follow the same pattern directly.

This may also just demonstrate my total lack of understanding of PGs intervals.

Jesper




pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: Patch to add a primary key using an existing index
Next
From: Heikki Linnakangas
Date:
Subject: Re: Crash safe visibility map vs hint bits