database/postgres
database/postgres
1
0
Fork 0
mirror of https://github.com/postgres/postgres.git synced 2025-04-22 23:02:54 +03:00
Code

Further documentation tweaks for event triggers.

Browse Source 
Per discussion between Dimitri Fontaine, myself, and others.
This commit is contained in:
Robert Haas 2013-01-23 09:17:20 -05:00
parent 601e2935e2
commit f925c79b9f
1 changed files with 11 additions and 5 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

16
doc/src/sgml/event-trigger.sgml
View File

@ -41,14 +41,20 @@
mechanism does not support these object types.
<literal>ddl_command_start</> also occurs just before the execution of a
<literal>SELECT INTO</literal> command, since this is equivalent to
<literal>CREATE TABLE AS</literal>.
<literal>CREATE TABLE AS</literal>. The <literal>ddl_command_end</>
event occurs just after the execution of this same set of commands.
</para>
<para>
The <literal>ddl_command_end</> event occurs just before returning
control from the execution of a <literal>CREATE</>, <literal>ALTER</>,
or <literal>DROP</> command. It shares the same exceptions as
the <literal>ddl_command_start</> event.
Event triggers (like other functions) cannot be executed in an aborted
transaction. Thus, if a DDL command fails with an error, any associated
<literal>ddl_command_end</> triggers will not be executed. Conversely,
if a <literal>ddl_command_start</> trigger fails with an error, no
further event triggers will fire, and no attempt will be made to execute
the command itself. Similarly, if a <literal>ddl_command_end</> trigger
fails with an error, the effects of the DDL statement will be rolled
back, just as they would be in any other case where the containing
transaction aborts.
</para>
<para>