FYI: I tried setting the md5 field to '' in the whole table but that didn't fix the pg_dump issue. In the end I decided to drop the database and revert to my last successful backup. I'm now still reading in all tapes to reconstruct the latest database state.
Then you could experiment with trying to update the md5 field with new data.
> > > > > > > > Following up on the max(bigint), I tried > > > > SELECT md5 FROM public.file where fileid >2087994666; > > > > and got > > > > ERROR: compressed data is corrupted > > > > So it does look like those entries are killing it. Now for the > > million-dollar question: how do I get them out? > > Do you have recent previous backup? > > > > > Nico > > > > -- > > > > Nico De Ranter > > > > Operations Engineer > > > > > > -- > Adrian Klaver > adrian.klaver@aklaver.com <mailto:adrian.klaver@aklaver.com> > > > > -- > > Nico De Ranter > > Operations Engineer >