Ensure that BEFORE STATEMENT triggers fire the right number of times.
Commit 0f79440fb introduced mechanism to keep AFTER STATEMENT triggers
from firing more than once per statement, which was formerly possible
if more than one FK enforcement action had to be applied to a given
table. Add a similar mechanism for BEFORE STATEMENT triggers, so that
we don't have the unexpected situation of firing BEFORE STATEMENT
triggers more often than AFTER STATEMENT.
As with the previous patch, back-patch to v10.
Discussion: https://postgr.es/m/22315.1505584992@sss.pgh.pa.us
Branch
------
REL_10_STABLE
Details
-------
https://git.postgresql.org/pg/commitdiff/5cc23493195cbd2205d5e476e725657c0a29ea34
Modified Files
--------------
doc/src/sgml/ref/create_trigger.sgml | 14 ++++---
src/backend/commands/trigger.c | 72 ++++++++++++++++++++++++++++------
src/test/regress/expected/triggers.out | 12 ++++++
src/test/regress/sql/triggers.sql | 6 +++
4 files changed, 87 insertions(+), 17 deletions(-)
--
Sent via pgsql-committers mailing list (pgsql-committers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-committers
