From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Sven Klemm <sven(at)timescale(dot)com> |
Cc: | pgsql-bugs(at)lists(dot)postgresql(dot)org |
Subject: | Re: pg_event_trigger_ddl_commands fails with cache lookup failed |
Date: | 2021-02-28 00:20:59 |
Message-ID: | 540819.1614471659@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-bugs |
Sven Klemm <sven(at)timescale(dot)com> writes:
>> trg=# ALTER TABLE t ALTER COLUMN f1 DROP IDENTITY, ALTER COLUMN f1 SET
>> DATA TYPE bigint;
>> ERROR: XX000: cache lookup failed for relation 13476892
>> CONTEXT: PL/pgSQL function ddl_end() line 5 at FOR over SELECT rows
>> LOCATION: getRelationTypeDescription, objectaddress.c:4178
This is not what I'd call an adequate bug report. I guessed at what you
might have started from, but it works for me:
regression=# create table t (f1 int generated always as identity);
CREATE TABLE
regression=# ALTER TABLE t ALTER COLUMN f1 DROP IDENTITY, ALTER COLUMN f1 SET
DATA TYPE bigint;
ALTER TABLE
Having said that, this seems like it's in the same ball park as some
not-very-long-ago bug fixes in ALTER TABLE's sequence of operations.
Maybe you just need to update.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Sven Klemm | 2021-02-28 00:30:18 | Re: pg_event_trigger_ddl_commands fails with cache lookup failed |
Previous Message | Sven Klemm | 2021-02-27 22:32:07 | Re: pg_event_trigger_ddl_commands fails with cache lookup failed |