Jeff Janes <jeff.janes@gmail.com> writes:
> ... But really, I don't think such
> communication should be necessary, and the xlrec.all_visible_cleared
> and xlrec.new_all_visible_cleared fields are unneeded. Just assume
> they are true. It seems like the worst thing that can happen is that
> we call PageClearAllVisible when it is already cleared, which is
> hardly harmful (the blocks that have redo applied to them are already
> dirty, so a spurious clear doesn't cause unneeded IO)
Just to respond to that --- I spent awhile yesterday thinking the same
thing. But the value of those flags is to tell the WAL replay functions
whether they need to go and clear the corresponding bits in the
visibility map. Making them do that unconditionally for every
insert/update/delete would surely be a pretty big hit to the speed of
WAL replay, which already leaves a lot to be desired :-(
regards, tom lane