From: | Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | pgsql-bugs(at)lists(dot)postgresql(dot)org |
Subject: | Re: Bogus NULL object_name from pg_event_trigger_dropped_objects() |
Date: | 2021-11-15 15:48:10 |
Message-ID: | 202111151548.zbalpm4zpnjy@alvherre.pgsql |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-bugs |
On 2021-Nov-15, Tom Lane wrote:
> I chanced to experiment with the event trigger function shown in
> 9.29.2. Processing Objects Dropped by a DDL Command [1].
> I got
>
> et=# create table t1(f1 text primary key);
> CREATE TABLE
> et=# drop table t1;
> NOTICE: DROP TABLE dropped object: table public.t1 public.t1
> NOTICE: DROP TABLE dropped object: type public.t1 public.t1
> NOTICE: DROP TABLE dropped object: type public._t1 public.t1[]
> NOTICE: DROP TABLE dropped object: toast table pg_toast.pg_toast_38092 pg_toast.pg_toast_38092
> NOTICE: DROP TABLE dropped object: index pg_toast.pg_toast_38092_index pg_toast.pg_toast_38092_index
> NOTICE: DROP TABLE dropped object: table constraint public.<NULL> t1_pkey on public.t1
> NOTICE: DROP TABLE dropped object: index public.t1_pkey public.t1_pkey
> DROP TABLE
> et=#
>
> Note the faulty output for the pkey constraint. I've not looked
> for the cause.
Egad.
Looking ...
--
Álvaro Herrera PostgreSQL Developer — https://www.EnterpriseDB.com/
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2021-11-15 15:49:25 | Re: pg_restore depending on user functions |
Previous Message | Дмитрий Иванов | 2021-11-15 15:46:47 | Re: pg_restore depending on user functions |