"Florian G. Pflug" <[EMAIL PROTECTED]> writes:
> Martijn van Oosterhout wrote:
>> It's the t_ctid field of the tuple header. But I don't see what that
>> has to do with "WHERE CURRENT OF". That expression should return the
>> tuple visible to your transaction, not some updated version which you
>> won't be able to fetch. If you end up updating the old version, the
>> system will take care of finding the newer version if necessary.
> The problem is that the ctid of the tuple that "fetch" returned
> might not actually be the tuple that needs to be updated.
Martijn's got a point though: it's not clear that that needs any special
care on the part of WHERE CURRENT OF. It may be that the existing
EvalPlanQual machinery does everything that's needful. Is the example
you show really any different from updating a tuple that someone else
updated while your UPDATE was in progress? In both cases the EPQ
machinery will take care of chaining forward to the right version to
update.
regards, tom lane
---------------------------(end of broadcast)---------------------------
TIP 4: Have you searched our list archives?
http://archives.postgresql.org
