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

From: "Kevin Grittner" <Kevin(dot)Grittner(at)wicourts(dot)gov>
To: "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: "Heikki Linnakangas" <heikki(dot)linnakangas(at)enterprisedb(dot)com>, <pgsql-bugs(at)postgresql(dot)org>
Subject: Re: BUG #5989: Assertion failure on UPDATE of big value
Date: 2011-04-20 20:12:39
Message-ID: 4DAEF7E7020000250003CAD2@gw.wicourts.gov
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> "Kevin Grittner" <Kevin(dot)Grittner(at)wicourts(dot)gov> writes:
>> If I'm reading this correctly, it would appear that nobody has
>> updated anything to a TOASTed value in a build against HEAD in
>> testing *anything* in the last two and a half months. And the
>> regression tests don't include a single UPDATE to a TOASTed value
>> anywhere. That seems like a significant code coverage
>> deficiency.
>
>> Attached is a patch to cure the latter of these. I'm submitting
>> this separately since it seems a good idea regardless of what
>> happens with the related SSI issue.
>
> Hmm, is there much regression coverage for TOAST inserts or
> deletes either?

There didn't appear to be. The attached provides minimal testing of
user-facing behavior of TOAST insert, update, and delete. It's
pretty basic, but a lot better than having no tests for this at all.

I can't help feeling that there should be a toast.sql test file
which reaches deeper, but I'm not exactly sure how far that would
go.

-Kevin

Attachment Content-Type Size
test-toast-dml.patch text/plain 5.6 KB

In response to

Browse pgsql-bugs by date

  From Date Subject
Next Message Kevin Grittner 2011-04-20 20:43:17 Re: BUG #5990: 100% CPU reached
Previous Message Kevin Grittner 2011-04-20 19:39:54 Re: BUG #5989: Assertion failure on UPDATE of big value