Commit04f9b44

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 parent08cf04b commit04f9b44Copy full SHA for 04f9b44

File tree

-0

lines changed

-0

lines changed

Lines changed: 7 additions & 0 deletions

Original file line number	Diff line number	Diff line change
`@@ -2320,6 +2320,13 @@ ri_FetchConstraintInfo(Trigger *trigger, Relation trig_rel, bool rel_is_pk)`
`2320`	`2320`	`elog(ERROR,"wrong pg_constraint entry for trigger \"%s\" on table \"%s\"",`
`2321`	`2321`	`trigger->tgname,RelationGetRelationName(trig_rel));`
`2322`	`2322`	`}`
	`2323`	`+else`
	`2324`	`+{`
	`2325`	`+if (riinfo->fk_relid!=RelationGetRelid(trig_rel)\|\|`
	`2326`	`+riinfo->pk_relid!=trigger->tgconstrrelid)`
	`2327`	`+elog(ERROR,"wrong pg_constraint entry for trigger \"%s\" on table \"%s\"",`
	`2328`	`+trigger->tgname,RelationGetRelationName(trig_rel));`
	`2329`	`+}`
`2323`	`2330`
`2324`	`2331`	`returnriinfo;`
`2325`	`2332`	`}`

Comments

(0)