Tom Lane wrote:
>
>Also, for Mario and Barry: does this test case look anything like what
>your real applications do? In particular, do you ever do a SELECT FOR
>UPDATE in a transaction that commits some changes, but does not update
>or delete the locked-for-update row? If not, it's possible
> Also, for Mario and Barry: does this test case look anything like what
> your real applications do? In particular, do you ever do a SELECT FOR
> UPDATE in a transaction that commits some changes, but does not update
> or delete the locked-for-update row? If not, it's possible there are
> yet
I've been studying the "No one parent tuple was found" problem some
more, and I've realized there are actually two distinct problems that
manifest at the same place.
Here are test procedures for duplicating the problems on-demand (these
work in either 7.2 or CVS tip):
CASE 1 (transient failure):
