On Sat, 2025-04-26 at 16:54 -0600, Sbob wrote:
> > 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
>
> I did REINDEX and the error came back, however this last time when they
> informed me about the error they sent the select statement throwing the
> error and once I logged in I ran their select statement and it worked,
> no REINDEX had been run, and then I asked them to run it again and it
> worked for them as well
>
> So, the first option above is not the answer and I dont think anyone
> updated the row, their process is mostly reads but I will verify, so
> maybe the RAM issue? the servers are cloud VM's in a private cloud
Maybe. Check the hardware.
Or maybe it is as Tom says.
Yours,
Laurenz Albe
