Re: ALTER TABLE results in "ERROR: could not open relation with OID 43707388"

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Manuel Rigger <rigger(dot)manuel(at)gmail(dot)com>
Cc: PostgreSQL mailing lists <pgsql-bugs(at)lists(dot)postgresql(dot)org>
Subject: Re: ALTER TABLE results in "ERROR: could not open relation with OID 43707388"
Date: 2019-11-02 16:04:19
Message-ID: 31328.1572710659@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

I wrote:
> Manuel Rigger <rigger(dot)manuel(at)gmail(dot)com> writes:
>> CREATE TABLE t0(c0 INT);
>> CREATE UNIQUE INDEX i0 ON t0(c0);
>> ALTER TABLE t0 ADD PRIMARY KEY USING INDEX i0, ALTER c0 TYPE BIGINT;
>> -- unexpected: ERROR: could not open relation with OID 43707388

> The sequence of events here is that:
> 1. transformIndexConstraint looks up the index "i0" and saves its OID
> in the IndexStmt's indexOid field.
> 2. ALTER c0 TYPE BIGINT executes first, because of ALTER TABLE's
> pass design. It rebuilds the i0 index --- with a new OID.
> 3. ATExecAddIndexConstraint tries to look up i0 using the old OID.
> Kaboom.

FYI, the patch I posted at

https://www.postgresql.org/message-id/24573.1572647175%40sss.pgh.pa.us

fixes this (as well as your other similar complaint). I forgot to
add a regression test matching this case, but will do so later.

regards, tom lane

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Alexey Ermakov 2019-11-02 17:30:45 Re: BUG #16016: deadlock with startup process, AccessExclusiveLock on pg_statistic's toast table
Previous Message Tom Lane 2019-11-02 15:10:06 Re: BUG #16016: deadlock with startup process, AccessExclusiveLock on pg_statistic's toast table