Heikki Linnakangas <heikki.linnakan...@enterprisedb.com> writes:
> The immediate fix is trivial:
> --- a/src/backend/access/heap/heapam.c
> +++ b/src/backend/access/heap/heapam.c
> @@ -2859,7 +2859,7 @@ l2:
> * Any existing SIREAD locks on the old tuple must be linked to
> the new
> * tuple for conflict detection purposes.
> */
> - PredicateLockTupleRowVersionLink(relation, &oldtup, newtup);
> + PredicateLockTupleRowVersionLink(relation, &oldtup, heaptup);
Egad. If that's it, my confidence in the amount of testing SSI has
gotten has just dropped dramatically.
regards, tom lane
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-bugs
