From: Tom Lane <tgl@sss.pgh.pa.us>
To: Alvaro Herrera <alvherre@2ndquadrant.com>
cc: Naveen Kumar <naveenchowdaryon@gmail.com>,
        pgsql-admin@lists.postgresql.org
Subject: Re: ERROR: unexpected chunk number 452 (expected 0) for toast value
 94674063 in pg_toast_56980977
In-reply-to: <20180718195850.axhzokgbggoxpcmr@alvherre.pgsql>
References: <20180718195850.axhzokgbggoxpcmr@alvherre.pgsql>
Comments: In-reply-to Alvaro Herrera <alvherre@2ndquadrant.com>
	message dated "Wed, 18 Jul 2018 15:58:50 -0400"
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-ID: <23930.1531946405.1@sss.pgh.pa.us>
Date: Wed, 18 Jul 2018 16:40:05 -0400
Message-ID: <23931.1531946405@sss.pgh.pa.us>
Precedence: bulk

Alvaro Herrera <alvherre@2ndquadrant.com> writes:
> On 2018-Jul-18, Naveen Kumar wrote:
>> What could be the reason for bellow errors. Can one help me to fix this?
>> Error message from server: ERROR: unexpected chunk number
>> 452 (expected 0) for toast value 94674063 in pg_toast_56980977

> There are two related bugfixes in 9.6.9 (and all other versions released
> with it).  Maybe you'd do well to upgrade to the latest minor of
> whatever supported branch you're using, and then let's discuss more.

It would certainly be helpful to upgrade to latest minor if not there
already, not to mention tell us which PG version this is.  But I'm
not really convinced that the 0408e1ed5 bug matches this symptom.
That would've led to duplicate TOAST rows, but it's hard to see how
duplicates could produce the above.

I'm inclined to think that this is either a corrupt toast index
(which'd be fixable with REINDEX) or actually-missing TOAST data.
Either way, if it's due to a PG bug rather than storage system
malfeasance, it's some other bug than that one.

			regards, tom lane