| From: | "Dickson S(dot) Guedes" <listas(at)guedesoft(dot)net> |
|---|---|
| To: | Robert Haas <robertmhaas(at)gmail(dot)com> |
| Cc: | Dimitri Fontaine <dimitri(at)2ndquadrant(dot)fr>, Alvaro Herrera <alvherre(at)2ndquadrant(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Event Triggers: adding information |
| Date: | 2013-01-21 23:29:34 |
| Message-ID: | CAHHcrep1YjPLFWONsjeCtucBHkMPvmhaFQ_3LaezTWvRE7zJYg@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
2013/1/21 Robert Haas <robertmhaas(at)gmail(dot)com>:
> Another thing is that we might want to document that if a command
> errors out, ddl_command_end will never be reached; and perhaps also
> that if ddl_command_start errors out, the command itself will never be
> reached. Perhaps this is so obvious as to not bear mentioning, I
> don't know, but the thought crossed my mind that someone might fail to
> realize it.
I think that should be a mention about that in docs, someone could
expect that ddl_command_end be reached even when
ddl_command_start erros out, and try to use it in some way.
Regards,
--
Dickson S. Guedes
mail/xmpp: guedes(at)guedesoft(dot)net - skype: guediz
http://github.com/guedes - http://guedesoft.net
http://www.postgresql.org.br
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2013-01-22 00:00:07 | Re: Prepared statements fail after schema changes with surprising error |
| Previous Message | Peter van Hardenberg | 2013-01-21 23:25:07 | Prepared statements fail after schema changes with surprising error |