pgsql: Fix AfterTriggerSaveEvent to use a test and elog, not just - Mailing list pgsql-committers

From tgl@postgresql.org (Tom Lane)
Subject pgsql: Fix AfterTriggerSaveEvent to use a test and elog, not just
Date
Msg-id 20091027201427.3DD85753FB7@cvs.postgresql.org
Whole thread Raw
List pgsql-committers
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.

Modified Files:
--------------
    pgsql/src/backend/commands:
        trigger.c (r1.255 -> r1.256)
        (http://anoncvs.postgresql.org/cvsweb.cgi/pgsql/src/backend/commands/trigger.c?r1=1.255&r2=1.256)

pgsql-committers by date:

Previous
From: tgl@postgresql.org (Tom Lane)
Date:
Subject: pgsql: Make FOR UPDATE/SHARE in the primary query not propagate into
Next
From: tgl@postgresql.org (Tom Lane)
Date:
Subject: pgsql: Fix AfterTriggerSaveEvent to use a test and elog, not just