| From: | Alvaro Herrera <alvherre(at)2ndquadrant(dot)com> |
|---|---|
| To: | Robert Haas <robertmhaas(at)gmail(dot)com> |
| Cc: | Dimitri Fontaine <dimitri(at)2ndquadrant(dot)fr>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: sql_drop Event Trigger |
| Date: | 2013-03-06 04:39:16 |
| Message-ID: | 20130306043916.GR9507@alvh.no-ip.org |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Alvaro Herrera escribió:
> Now, one last thing that comes up is what about objects that don't have
> straight names (such as pg_amop, pg_amproc, pg_default_acl etc etc), the
> only thing you get is a catalog OID and an object OID ... but they are
> pretty useless because by the time you get to the ddl_command_end
> trigger, the objects are gone from the catalog. Maybe we should report
> *something* about those.
Here's another idea --- have three columns, "type", "schema" (as in the
current patch and as shown above), and a third one for object identity.
For tables and other objects that have simple names, the identity would
be their names. For columns, it'd be <tablename>.<columnname>. For
functions, it'd be the complete signature. And so on.
--
Álvaro Herrera http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Training & Services
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Michael Paquier | 2013-03-06 04:48:47 | Re: Writable foreign tables: how to identify rows |
| Previous Message | Peter Eisentraut | 2013-03-06 04:37:17 | Re: pg_ctl idempotent option |