From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Peter Geoghegan <pg(at)bowt(dot)ie> |
Cc: | Andres Freund <andres(at)anarazel(dot)de>, PostgreSQL mailing lists <pgsql-bugs(at)lists(dot)postgresql(dot)org>, deathlock13(at)gmail(dot)com |
Subject: | Re: BUG #15309: ERROR: catalog is missing 1 attribute(s) for relid 760676 when max_parallel_maintenance_workers > 0 |
Date: | 2018-08-03 17:58:46 |
Message-ID: | 26037.1533319126@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-bugs |
Peter Geoghegan <pg(at)bowt(dot)ie> writes:
> On Fri, Aug 3, 2018 at 10:11 AM, Andres Freund <andres(at)anarazel(dot)de> wrote:
>> Maybe I'm missing something, but doesn't that error likely point to a bug in the new parallel index creation code, rather than the created indexes?
> I've certainly seen error messages like that with cases of
> catalog corruption. I recall repairing pg_attribute by hand when this
> happened, and then having to reindex the system catalogs.
> I don't really know what's wrong here, but I wouldn't be surprised if
> amcheck detected a problem. Let's see.
I think the OP's time would be more usefully spent on creating a
submittable test case. We will want that whether or not amcheck
complains, because the mere fact of the complaint is not likely to be
enough to find the problem. (I do agree that this smells like a problem
in parallel index build.)
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Peter Geoghegan | 2018-08-03 18:03:51 | Re: BUG #15309: ERROR: catalog is missing 1 attribute(s) for relid 760676 when max_parallel_maintenance_workers > 0 |
Previous Message | Peter Geoghegan | 2018-08-03 17:29:54 | Re: BUG #15309: ERROR: catalog is missing 1 attribute(s) for relid 760676 when max_parallel_maintenance_workers > 0 |