Horton

Fix SET CONSTRAINTS .. DEFERRED on partitioned tables

Alvaro Herrera <alvherre@alvh.no-ip.org>

View on postgr.es
Commit: b75ccddcd6f747dc386411eeac6bbfdface14a2c
Author: Alvaro Herrera <alvherre@alvh.no-ip.org>
Date: 2019-11-07T16:59:24Z
Releases: 12.1 
Fix SET CONSTRAINTS .. DEFERRED on partitioned tables

SET CONSTRAINTS ... DEFERRED failed on partitioned tables, because of a
sanity check that ensures that the affected constraints have triggers.
On partitioned tables, the triggers are in the leaf partitions, not in
the partitioned relations themselves, so the sanity check fails.
Removing the sanity check solves the problem, because the code needed to
support the case is already there.

Backpatch to 11.

Note: deferred unique constraints are not affected by this bug, because
they do have triggers in the parent partitioned table.  I did not add a
test for this scenario.

Discussion: https://postgr.es/m/20191105212915.GA11324@alvherre.pgsql

Files

PathChange+/−
src/backend/commands/trigger.c modified +0 −10
src/test/regress/expected/foreign_key.out modified +53 −3
src/test/regress/sql/foreign_key.sql modified +44 −1

Discussion