Re: BUG #15528: on v11.0 version still get error "ERROR: catalog is missing 1 attribute(s) for relid 6855092"

when set max_parallel_maintenance_workers = 0,no issue(vacuum full ok)now.before it my 2 times test were all failed.now I set it to 2 again and set log_min_message = debug5,log_min_error_statement=debug5,try to get more details.

---Original---
From: "Peter Geoghegan"<pg(at)bowt(dot)ie>
Date: Sat, Dec 1, 2018 14:14 PM
To: "zxw110876189"<zxw110876189(at)qq(dot)com>;
Cc: "PostgreSQL mailing lists"<pgsql-bugs(at)lists(dot)postgresql(dot)org>;
Subject: Re: BUG #15528: on v11.0 version still get error "ERROR: catalog is missing 1 attribute(s) for relid 6855092"

On Fri, Nov 30, 2018 at 9:52 PM Peter Geoghegan <pg(at)bowt(dot)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