From: | Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org> |
---|---|
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 16:16:06 |
Message-ID: | 20210228161606.GA21845@alvherre.pgsql |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-bugs |
On 2021-Feb-27, Sven Klemm wrote:
> Hello,
>
> > 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
>
> Is this expected behaviour or something that should be fixed?
> The documentation for pg_event_trigger_ddl_commands doesnt mention
> that it could fail for certain statements.
Yeah, this is certainly a bug. The code should likely ignore the
sub-command. I'll have a look.
--
Álvaro Herrera Valdivia, Chile
"After a quick R of TFM, all I can say is HOLY CR** THAT IS COOL! PostgreSQL was
amazing when I first started using it at 7.2, and I'm continually astounded by
learning new features and techniques made available by the continuing work of
the development team."
Berend Tober, http://archives.postgresql.org/pgsql-hackers/2007-08/msg01009.php
From | Date | Subject | |
---|---|---|---|
Next Message | goodluck.deep989 | 2021-02-28 19:12:41 | Bug : Did't show Constaint violation error |
Previous Message | Tom Lane | 2021-02-28 00:35:23 | Re: pg_event_trigger_ddl_commands fails with cache lookup failed |