Commit815b20a

committed

Restore RI trigger sanity check

I unnecessarily removed this check in3de241d because Imisunderstood what the final representation of constraints across apartitioning hierarchy was to be. Put it back (in both branches).Discussion:https://postgr.es/m/201901222145.t6wws6t6vrcu@alvherre.pgsql

1 parentc1afd17 commit815b20aCopy full SHA for 815b20a

File tree

-0

lines changed

-0

lines changed

Lines changed: 7 additions & 0 deletions

Original file line number	Diff line number	Diff line change
`@@ -1739,6 +1739,13 @@ ri_FetchConstraintInfo(Trigger *trigger, Relation trig_rel, bool rel_is_pk)`
`1739`	`1739`	`elog(ERROR,"wrong pg_constraint entry for trigger \"%s\" on table \"%s\"",`
`1740`	`1740`	`trigger->tgname,RelationGetRelationName(trig_rel));`
`1741`	`1741`	`}`
	`1742`	`+else`
	`1743`	`+{`
	`1744`	`+if (riinfo->fk_relid!=RelationGetRelid(trig_rel)\|\|`
	`1745`	`+riinfo->pk_relid!=trigger->tgconstrrelid)`
	`1746`	`+elog(ERROR,"wrong pg_constraint entry for trigger \"%s\" on table \"%s\"",`
	`1747`	`+trigger->tgname,RelationGetRelationName(trig_rel));`
	`1748`	`+}`
`1742`	`1749`
`1743`	`1750`	`if (riinfo->confmatchtype!=FKCONSTR_MATCH_FULL&&`
`1744`	`1751`	`riinfo->confmatchtype!=FKCONSTR_MATCH_PARTIAL&&`

Comments

(0)