Re: BUG #15597: possible bug in amcheck/amcheck_next (or corrupted index?)

On Fri, Jan 25, 2019 at 9:57 AM Peter Geoghegan <pg@bowt.ie> wrote:
> I have a draft patch that fixes this, but I haven't quite decided if I
> want to commit to the approach I've taken to normalizing TOASTed
> tuples. I will definitely fix the externally maintained version
> (amcheck_next) once this is settled. Thanks for the report.

I pushed a fix for this to contrib/amcheck, and to the externally
maintained amcheck_next codebase. There will be new set of point
releases of Postgres on February 14th, 2019. I'll see to cutting a new
release of amcheck_next shortly as well.

Thanks for the report!
-- 
Peter Geoghegan