Re: BUG #5989: Assertion failure on UPDATE of big value

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Heikki Linnakangas <heikki(dot)linnakangas(at)enterprisedb(dot)com>
Cc: pgsql-bugs(at)postgresql(dot)org
Subject: Re: BUG #5989: Assertion failure on UPDATE of big value
Date: 2011-04-20 15:26:11
Message-ID: 27328.1303313171@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

Heikki Linnakangas <heikki(dot)linnakangas(at)enterprisedb(dot)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

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Kevin Grittner 2011-04-20 15:26:57 Re: BUG #5989: Assertion failure on UPDATE of big value
Previous Message Heikki Linnakangas 2011-04-20 15:12:38 Re: BUG #5989: Assertion failure on UPDATE of big value