Dennis Gearon <gearond(at)cvc(dot)net> writes:
> No one going to bite on this? Any developers have any idea what goes
> on in the code for committment?
Knowing what the code does today is not the same thing as wanting to
promise that it will always do that. In general, writing an application
that depends on trigger firing order is bad application design IMHO.
regards, tom lane