On 05.09.2013 20:30, Alvaro Herrera wrote:
> I was scrolling heapgettup() and heapgettup_pagemode() in parallel, and
> noticed that the former calls CheckForSerializableConflictOut() for
> tuples read, and the latter doesn't. Is there a reason for this
> discrepancy? If so, I think it warrants a comment about the missing
> check.
In page-at-a-time mode, the CheckForSerializableConflictOut() is done in
heapgetpage(). Same with the visibility checks.
- Heikki