Index: doc/src/sgml/ref/create_trigger.sgml
===================================================================
RCS file: /cvsroot/pgsql/doc/src/sgml/ref/create_trigger.sgml,v
retrieving revision 1.42
diff -c -c -r1.42 create_trigger.sgml
*** doc/src/sgml/ref/create_trigger.sgml	1 Nov 2005 21:09:50 -0000	1.42
--- doc/src/sgml/ref/create_trigger.sgml	9 Dec 2005 19:38:27 -0000
***************
*** 241,253 ****
        function that executes the desired commands.
       </para>
      </listitem>
     </itemizedlist>
    </para>
  
    <para>
     SQL specifies that multiple triggers should be fired in
     time-of-creation order.  <productname>PostgreSQL</productname> uses
!    name order, which was judged more convenient to work with.
    </para>
  
    <para>
--- 241,265 ----
        function that executes the desired commands.
       </para>
      </listitem>
+ 
     </itemizedlist>
    </para>
  
    <para>
     SQL specifies that multiple triggers should be fired in
     time-of-creation order.  <productname>PostgreSQL</productname> uses
!    name order, which was judged to be more convenient.
!   </para>
! 
!   <para>
!    SQL specifies that <literal>BEFORE DELETE</literal> triggers on cascaded
!    deletes fire <emphasis>after</> the cascaded <literal>DELETE</> completes.
!    The <productname>PostgreSQL</productname> behavior is for <literal>BEFORE
!    DELETE</literal> to always fire before the delete action, even a cascading
!    one.  This is considered more consistent.  There is also unpredictable
!    behavior when <literal>BEFORE</literal> triggers modify rows that are later
!    to be modified by referential actions.  This can lead to contraint violations
!    or stored data that does not honor the referential constraint.
    </para>
  
    <para>