On Sun, Jan 28, 2018 at 06:12:01PM -0500, Tom Lane wrote: > Bruce Momjian <br...@momjian.us> writes: > > Oh, I am sorry. I was focused on the first part of the sentence and > > didn't notice your change to the second part. How is this attachment? > > Seems same as your previous version?
OK, new vesion that uses "explicitly named" in both modified doc lines. -- Bruce Momjian <br...@momjian.us> http://momjian.us EnterpriseDB http://enterprisedb.com + As you are, so once was I. As I am, so you will be. + + Ancient Roman grave inscription +
diff --git a/doc/src/sgml/ref/create_trigger.sgml b/doc/src/sgml/ref/create_trigger.sgml new file mode 100644 index a8c0b57..dab1041 *** a/doc/src/sgml/ref/create_trigger.sgml --- b/doc/src/sgml/ref/create_trigger.sgml *************** UPDATE OF <replaceable>column_name1</rep *** 501,509 **** <para> Modifying a partitioned table or a table with inheritance children fires ! statement-level triggers directly attached to that table, but not statement-level triggers for its partitions or child tables. In contrast, ! row-level triggers are fired for all affected partitions or child tables. If a statement-level trigger has been defined with transition relations named by a <literal>REFERENCING</literal> clause, then before and after images of rows are visible from all affected partitions or child tables. --- 501,510 ---- <para> Modifying a partitioned table or a table with inheritance children fires ! statement-level triggers attached to the explicitly named table, but not statement-level triggers for its partitions or child tables. In contrast, ! row-level triggers are fired on the rows in effected partitions or ! child tables, even if they are not explicitly named in the query. If a statement-level trigger has been defined with transition relations named by a <literal>REFERENCING</literal> clause, then before and after images of rows are visible from all affected partitions or child tables.