Thread: pgsql: Fix AfterTriggerSaveEvent to use a test and elog, not just

pgsql: Fix AfterTriggerSaveEvent to use a test and elog, not just

From

tgl@postgresql.org (Tom Lane)

Date:

27 October 2009, 17:15:08

Log Message:
-----------
Fix AfterTriggerSaveEvent to use a test and elog, not just Assert, to check
that it's called within an AfterTriggerBeginQuery/AfterTriggerEndQuery pair.
The RI cascade triggers suppress that overhead on the assumption that they
are always run non-deferred, so it's possible to violate the condition if
someone mistakenly changes pg_trigger to mark such a trigger deferred.
We don't really care about supporting that, but throwing an error instead
of crashing seems desirable.  Per report from Marcelo Costa.

Tags:
----
REL8_1_STABLE

Modified Files:
--------------
    pgsql/src/backend/commands:
        trigger.c (r1.195.2.6 -> r1.195.2.7)
        (http://anoncvs.postgresql.org/cvsweb.cgi/pgsql/src/backend/commands/trigger.c?r1=1.195.2.6&r2=1.195.2.7)