Commit5b64838

committed

doc: clearify trigger behavior for inheritance

The previous wording added in PG 10 wasn't specific enough about thebehavior of statement and row triggers when using inheritance.Reported-by: ian@thepathcentral.comDiscussion:https://postgr.es/m/20171129193934.27108.30796@wrigleys.postgresql.orgBackpatch-through: 10

1 parent19eb7f8 commit5b64838Copy full SHA for 5b64838

File tree

-2

lines changed

-2

lines changed

Lines changed: 3 additions & 2 deletions

Original file line number	Diff line number	Diff line change
`@@ -501,9 +501,10 @@ UPDATE OF <replaceable>column_name1</replaceable> [, <replaceable>column_name2</`
`501`	`501`
`502`	`502`	`<para>`
`503`	`503`	`Modifying a partitioned table or a table with inheritance children fires`
`504`		`- statement-level triggersdirectlyattached tothat table, but not`
	`504`	`+ statement-level triggers attached tothe explicitly named table, but not`
`505`	`505`	`statement-level triggers for its partitions or child tables. In contrast,`
`506`		`- row-level triggers are fired for all affected partitions or child tables.`
	`506`	`+ row-level triggers are fired on the rows in effected partitions or`
	`507`	`+ child tables, even if they are not explicitly named in the query.`
`507`	`508`	`If a statement-level trigger has been defined with transition relations`
`508`	`509`	`named by a <literal>REFERENCING</literal> clause, then before and after`
`509`	`510`	`images of rows are visible from all affected partitions or child tables.`

Comments

(0)