devik(at)cdi(dot)cz writes:
> Ahh I did not know that there is need to test tuple for
> validity for some past cid. I thought that we only need
> to know whether tuple has been updated by current cid
> to ensure that it will not be scanned again in the same
> cid... Where am I wrong ?
In situations like SQL function calls, it may be necessary to suspend
a table scan while we go off and do other commands, then come back and
resume the table scan. So there can be multiple scans with different
command IDs in progress within a transaction.
regards, tom lane