| From: | Robert Haas <robertmhaas(at)gmail(dot)com> |
|---|---|
| To: | Alvaro Herrera <alvherre(at)2ndquadrant(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-05 13:24:46 |
| Message-ID: | CA+Tgmoaj2C7mxz4yiZyXWspfUP61i2deZ=GERdbU0sA8=hOB-A@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Mon, Mar 4, 2013 at 11:13 AM, Alvaro Herrera
<alvherre(at)2ndquadrant(dot)com> wrote:
> Another question. If I do ALTER TABLE foo DROP COLUMN bar, do we need
> to fire an event trigger for the dropped column? Right now we don't,
> ISTM we should. And if we want that, then the above set of three
> properties doesn't cut it.
+1. Similar questions arise for object-access-hooks, among other places.
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Robert Haas | 2013-03-05 13:30:56 | Re: sql_drop Event Trigger |
| Previous Message | Fujii Masao | 2013-03-05 13:12:46 | Re: odd behavior in materialized view |