On Sunday, September 14, 2025, Chao Li <
li.evan.chao@gmail.com> wrote:
It says that UPDATE will only find target rows that were committed as of the command start time. I think the statement implies that an “update” statement will never update a “future” tuple.
It will indeed see a future physical tuple so long as the logical row that said tuple refers to already was committed, and it found the corresponding past physical tuple.
Admittedly, I’m unclear on how exactly the system communicates/understands that the past and future physical tuples refer to same logical row reliably. In the docs, one is left to assume that feature just works.
David J.