| From: | Peter Eisentraut <peter_e(at)gmx(dot)net> |
|---|---|
| To: | Dimitri Fontaine <dimitri(at)2ndQuadrant(dot)fr> |
| Cc: | Alvaro Herrera <alvherre(at)2ndquadrant(dot)com>, Robert Haas <robertmhaas(at)gmail(dot)com>, "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: event trigger API documentation? |
| Date: | 2013-06-20 01:08:33 |
| Message-ID: | 1371690513.13762.32.camel@vanquo.pezone.net |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Random observation in this general area: Regular triggers provide the
field Trigger *tg_trigger in the trigger data, which allows you to get
the trigger name, OID, and such. Event triggers don't expose anything
comparable. That should perhaps be added.
Also, as I'm maybe about the fourth person ever to write an actual event
trigger, I have a usability report of sorts. I found it confusing that
the trigger timing is encoded into the event name. So instead of ON
ddl_command_start, I was expecting something more like BEFORE
ddl_command. There might be a reason for this design choice, but I
found it a confusing departure from known trigger concepts.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Peter Eisentraut | 2013-06-20 01:19:18 | slightly confusing JSON error context |
| Previous Message | Claudio Freire | 2013-06-20 00:04:12 | Re: Implementing incremental backup |