postgres.git / summary / log / commit / refs

commit    04f9b449aa309410dbbcbf4951802a3f73b42bd0
Author:   Alvaro Herrera <alvherre@alvh.no-ip.org>
Date:     Wed Mar 20 20:23:26 2019 +0000
First released in: 12.0, 11.3

    Restore RI trigger sanity check
    
    I unnecessarily removed this check in 3de241dba86f because I
    misunderstood what the final representation of constraints across a
    partitioning hierarchy was to be.  Put it back (in both branches).
    
    Discussion: https://postgr.es/m/201901222145.t6wws6t6vrcu@alvherre.pgsql


 src/backend/utils/adt/ri_triggers.c | 7 +++++++
 1 file changed, 7 insertions(+)

diff --git a/src/backend/utils/adt/ri_triggers.c b/src/backend/utils/adt/ri_triggers.c
index cfc25c55dfa..d3225094c7a 100644
--- a/src/backend/utils/adt/ri_triggers.c
+++ b/src/backend/utils/adt/ri_triggers.c
@@ -2320,6 +2320,13 @@ ri_FetchConstraintInfo(Trigger *trigger, Relation trig_rel, bool rel_is_pk)
 			elog(ERROR, "wrong pg_constraint entry for trigger \"%s\" on table \"%s\"",
 				 trigger->tgname, RelationGetRelationName(trig_rel));
 	}
+	else
+	{
+		if (riinfo->fk_relid != RelationGetRelid(trig_rel) ||
+			riinfo->pk_relid != trigger->tgconstrrelid)
+			elog(ERROR, "wrong pg_constraint entry for trigger \"%s\" on table \"%s\"",
+				 trigger->tgname, RelationGetRelationName(trig_rel));
+	}
 
 	return riinfo;
 }


[parent: 08cf04bb4747]