public inbox for [email protected]  

help / color / mirror / Atom feed

From: Laurenz Albe <[email protected]>
To: Sbob <[email protected]>
To: [email protected]
Subject: Re: Intermittent missing chunk ERRORS
Date: Sat, 26 Apr 2025 22:24:58 +0200
Message-ID: <[email protected]> (raw)
In-Reply-To: <[email protected]>
References: <[email protected]>

On Sat, 2025-04-26 at 11:09 -0600, Sbob wrote:
> I am working with a client, they have an app that is running into error's like this:
> 
> SQL Error [XX001]: ERROR: missing chunk number 0 for toast value 44915477 in pg_toast_5321896 
> 
> I thought it was a corruption / REINDEX issue, however I have run REINDEXon the index,
> REINDEX on the table and even a reindexdb on the database. Today they passed me another
> error (the one above) and once I was able to login I ran the same query the app team
> referenced and it ran without any errors. I asked them to re-run the query and they
> informed me that it now works for them as well.
> 
> I assume that if this were a corrupt index issue then the query would continue to fail
> every time.
> 
> Has anyone seen this type of intermittent index error before? and thoughts on where to
> look /how to debug this?

The error is data corruption.

If it is transient, that could mean a couple of things:

- a TOAST index was corrupted, and REINDEX fixed it

- faulty RAM corrupted data, but as soon as the corrupted buffer was evicted,
  the problem was gone

- somebody updated or deleted the row, and the corruption is hidden

Yours,
Laurenz Albe

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: [email protected]
  Cc: [email protected], [email protected], [email protected]
  Subject: Re: Intermittent missing chunk ERRORS
  In-Reply-To: <[email protected]>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox