Re: "failed to find parent tuple for heap-only tuple" error as an ERRCODE_DATA_CORRUPTION ereport()

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Peter Geoghegan <pg(at)bowt(dot)ie>
Cc: David Steele <david(at)pgmasters(dot)net>, Andres Freund <andres(at)anarazel(dot)de>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>
Subject: Re: "failed to find parent tuple for heap-only tuple" error as an ERRCODE_DATA_CORRUPTION ereport()
Date: 2018-03-01 21:04:56
Message-ID: 24145.1519938296@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Peter Geoghegan <pg(at)bowt(dot)ie> writes:
> On Thu, Mar 1, 2018 at 11:23 AM, David Steele <david(at)pgmasters(dot)net> wrote:
>> Yes, I agree. My thrust was more to discover if there is any testing
>> for these conditions being done in core. It sounds like no, but I don't
>> think it's the responsibility of this patch to add them.

> The only tests possible with stock Postgres are performed by CREATE
> INDEX/REINDEX.

Yeah, I see no practical way to test this error case, and little point in
asking this patch to do anything about it. If we had some test rig for
injecting corrupted data, it might be interesting to look at ...

Patch looks fine to me, will push.

regards, tom lane

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Andres Freund 2018-03-01 21:11:54 Re: WIP Patch: Precalculate stable functions, infrastructure v1
Previous Message Andres Freund 2018-03-01 21:01:38 Re: MCV lists for highly skewed distributions