Re: BUG #15528: on v11.0 version still get error "ERROR: catalog ismissing 1 attribute(s) for relid 6855092" - Mailing list pgsql-bugs

From Peter Geoghegan
Subject Re: BUG #15528: on v11.0 version still get error "ERROR: catalog ismissing 1 attribute(s) for relid 6855092"
Date
Msg-id CAH2-WzkKG0A6p-h0Sc8qCeAZdjz17f2L52br7-ZJRNDCL+A=Hg@mail.gmail.com
Whole thread Raw
In response to Re: BUG #15528: on v11.0 version still get error "ERROR: catalog ismissing 1 attribute(s) for relid 6855092"  (Peter Geoghegan <pg@bowt.ie>)
List pgsql-bugs
On Fri, Nov 30, 2018 at 9:52 PM Peter Geoghegan <pg@bowt.ie> wrote:
> Using amcheck would let us know if the index is completely corrupt
> (e.g. tuples are in the wrong order), or if the duplicate is garbage
> that has somehow become visible again, a symptom of bugs which is also
> possible. It's easy to use amcheck. Maybe there is another bug that is
> similar to #15309, but we need to establish if the index is truly
> corrupt, and what it looks like. It would also be good to use
> contrib/pageinspect to look at any blocks that amcheck shows in an
> error message.

Also, can you confirm that the problem goes away when
max_parallel_maintenance_workers is set to 0? That's what we saw with
bug #15309.

-- 
Peter Geoghegan


pgsql-bugs by date:

Previous
From: Peter Geoghegan
Date:
Subject: Re: BUG #15528: on v11.0 version still get error "ERROR: catalog ismissing 1 attribute(s) for relid 6855092"
Next
From: Lulzim Bilali
Date:
Subject: Re: BUG #15533: error on upsert when used in a fuction and a functionparameter has the same name as the column