Re: Fix missing EvalPlanQual recheck for TID scans - Mailing list pgsql-hackers

From David Rowley
Subject Re: Fix missing EvalPlanQual recheck for TID scans
Date
Msg-id CAApHDvqNH8AObaQh6PrDq_-X7Zg5G6hN4GeB7DYw84z3bc7kKg@mail.gmail.com
Whole thread Raw
In response to Re: Fix missing EvalPlanQual recheck for TID scans  (Chao Li <li.evan.chao@gmail.com>)
Responses Re: Fix missing EvalPlanQual recheck for TID scans
List pgsql-hackers
On Mon, 15 Sept 2025 at 17:32, Chao Li <li.evan.chao@gmail.com> wrote:
> UPDATE, DELETE, SELECT FOR UPDATE, and SELECT FOR SHARE commands behave the same as SELECT in terms of searching for
targetrows: they will only find target rows that were committed as of the command start time. 
>
> It says that UPDATE will only find target rows that were committed as of the command start time. I think the
statementimplies that an “update” statement will never update a “future” tuple. 

I think you've only read the first sentence in that paragraph. Please
read the entire paragraph. You'll see it goes on to explain "it will
attempt to apply its operation to the updated version of the row".

David



pgsql-hackers by date:

Previous
From: "David G. Johnston"
Date:
Subject: Re: Fix missing EvalPlanQual recheck for TID scans
Next
From: Peter Eisentraut
Date:
Subject: Re: [PATCH] jit: fix build with LLVM-21