Re: ERROR: unexpected chunk number 0 (expected 1) for toast value76753264 in pg_toast_10920100 - Mailing list pgsql-general

From Michael Paquier
Subject Re: ERROR: unexpected chunk number 0 (expected 1) for toast value76753264 in pg_toast_10920100
Date
Msg-id 20180118013957.GD29962@paquier.xyz
Whole thread Raw
In response to Re: ERROR: unexpected chunk number 0 (expected 1) for toast value 76753264 in pg_toast_10920100  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-general
On Wed, Jan 17, 2018 at 12:16:19PM -0500, Tom Lane wrote:
> The basic thrust of these messages is "I'm reading what should be
> sequentially numbered data chunks for this toast OID, and the sequence
> numbers are wrong".  Both of these instances could be explained by
> duplicate toast rows (or duplicate index entries pointing at one row),
> though of course that would just move to the next question of how it
> got that way.

Good point here. This could be a consequence of freeze-the-dead whose
fix will be available in the next round of minor releases.
--
Michael

Attachment

pgsql-general by date:

Previous
From: Jacek Kołodziej
Date:
Subject: Re: READ COMMITTED vs. index-only scans
Next
From: Nikolay
Date:
Subject: Partitioning constraints vs before-trigger