Date: Mon, 15 Nov 2021 12:48:10 -0300
From: Alvaro Herrera <alvherre@alvh.no-ip.org>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: pgsql-bugs@lists.postgresql.org
Subject: Re: Bogus NULL object_name from pg_event_trigger_dropped_objects()
Message-ID: <202111151548.zbalpm4zpnjy@alvherre.pgsql>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
In-Reply-To: <2123408.1636990185@sss.pgh.pa.us>
Archived-At: 
 <https://www.postgresql.org/message-id/202111151548.zbalpm4zpnjy%40alvherre.pgsql>
Precedence: bulk

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/