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

From: Peter Geoghegan <pg(at)bowt(dot)ie>
To: David Steele <david(at)pgmasters(dot)net>
Cc: 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 20:01:24
Message-ID: CAH2-WznagAJQLu=G6EWxPGYDxq2iL=5iAwx68uiNF1_-tzS_-Q@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

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. That generally isn't practical as a general smoke test,
not least because you cannot do a CREATE INDEX on a standby -- unlike
the amcheck heapallindexed test.

--
Peter Geoghegan

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Andres Freund 2018-03-01 20:01:29 Re: Protect syscache from bloating with negative cache entries
Previous Message Robert Haas 2018-03-01 19:49:26 Re: Protect syscache from bloating with negative cache entries