From: | Sven Klemm <sven(at)timescale(dot)com> |
---|---|
To: | pgsql-hackers(at)lists(dot)postgresql(dot)org, Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org> |
Subject: | Re: Fix dropped object handling in pg_event_trigger_ddl_commands |
Date: | 2021-04-25 10:20:06 |
Message-ID: | CAMCrgp1gsSa2rco-6TDAXiFUv83dTgUsAvzANzzGFUoNPOECWg@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Sun, Apr 18, 2021 at 2:12 PM Sven Klemm <sven(at)timescale(dot)com> wrote:
> when creating an event trigger for ddl_command_end that calls
> pg_event_trigger_ddl_commands certain statements will cause the
> trigger to fail with a cache lookup error. The error happens on
> master, 13 and 12 I didnt test any previous versions.
>
> trg=# ALTER TABLE t ALTER COLUMN f1 SET DATA TYPE bigint, ALTER COLUMN
> f1 DROP IDENTITY;
> 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
Any opinions on the patch? Is this not worth the effort to fix or is
there a better way to fix this?
--
Regards, Sven Klemm
From | Date | Subject | |
---|---|---|---|
Next Message | Noah Misch | 2021-04-25 10:24:19 | Re: Allowing to create LEAKPROOF functions to non-superuser |
Previous Message | Julien Rouhaud | 2021-04-25 08:22:51 | Re: compute_query_id and pg_stat_statements |