From: | "Jesper(at)Krogh(dot)cc" <jesper(at)krogh(dot)cc> |
---|---|
To: | "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Crash safe visibility map vs hint bits |
Date: | 2010-12-04 07:14:45 |
Message-ID: | 41D1FA6A-4C19-4266-833F-9AF585ECD70C@krogh.cc |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
There has been a lot discussion about index-only scans and how to make the visibillity map crash safe. Then followed by a good 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 looks more 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 recovery jobs 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
From | Date | Subject | |
---|---|---|---|
Next Message | Heikki Linnakangas | 2010-12-04 07:48:25 | Re: Crash safe visibility map vs hint bits |
Previous Message | Tom Lane | 2010-12-04 06:30:09 | Re: Patch to add a primary key using an existing index |