| From: | Luca Ferrari <fluca1978(at)gmail(dot)com> |
|---|---|
| To: | Miles Elam <miles(dot)elam(at)productops(dot)com> |
| Cc: | PG-General Mailing List <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: Event Triggers and Dropping Objects |
| Date: | 2019-10-05 08:50:14 |
| Message-ID: | CAKoxK+7Kk7n_0f6xS4ygGBDadc6=-8U8RK_uz7Lv+x2NVMvKTA@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On Fri, Oct 4, 2019 at 10:38 PM Miles Elam <miles(dot)elam(at)productops(dot)com> wrote:
>
> The event trigger firing matrix lists tags like DROP TABLE and DROP FUNCTION are listed below the ddl_command_end event, but when I created a basic audit table and event trigger, they don't seem to fire. I know sql_drop exists, but again the matrix lists DROP commands in the ddl_command_end event.
Yes, I think this is a little misleading:
<https://www.postgresql.org/docs/11/event-trigger-matrix.html>.
The ddl_command_end is issued, and the function is invoked, but
pg_event_trigger_ddl_commands() returns NULL on such invocation
because sql_drop is the event with the attached data.
Hope this helps,
Luca
| From | Date | Subject | |
|---|---|---|---|
| Next Message | PegoraroF10 | 2019-10-05 11:34:31 | Re: Performance on JSONB select |
| Previous Message | Bruce Momjian | 2019-10-04 22:19:34 | Re: Clarification on the release notes of postgresql 12 regarding pg_upgrade |