Postgres Pro
Downloads
Home   >   mailing lists

Re: "failed to find parent tuple for heap-only tuple" error as anERRCODE_DATA_CORRUPTION ereport() - Mailing list pgsql-hackers

From Peter Geoghegan
Subject Re: "failed to find parent tuple for heap-only tuple" error as anERRCODE_DATA_CORRUPTION ereport()
Date
Msg-id CAH2-WznagAJQLu=G6EWxPGYDxq2iL=5iAwx68uiNF1_-tzS_-Q@mail.gmail.com
Whole thread Raw
In response to Re: "failed to find parent tuple for heap-only tuple" error as anERRCODE_DATA_CORRUPTION ereport()  (David Steele <david@pgmasters.net>)
Responses Re: "failed to find parent tuple for heap-only tuple" error as an ERRCODE_DATA_CORRUPTION ereport()  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
Tree view 
On Thu, Mar 1, 2018 at 11:23 AM, David Steele <david@pgmasters.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

pgsql-hackers by date:

Previous
From: Robert Haas
Date:
Subject: Re: Protect syscache from bloating with negative cache entries
Next
From: Andres Freund
Date:
Subject: Re: Protect syscache from bloating with negative cache entries