Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.89) (envelope-from ) id 1efwCT-0008LK-OV for pgsql-docs@arkaria.postgresql.org; Sun, 28 Jan 2018 23:17:25 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.84_2) (envelope-from ) id 1efwCS-00033u-KT for pgsql-docs@arkaria.postgresql.org; Sun, 28 Jan 2018 23:17:24 +0000 Received: from makus.postgresql.org ([2001:4800:1501:1::229]) by malur.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.84_2) (envelope-from ) id 1efwCS-00033k-Bq for pgsql-docs@lists.postgresql.org; Sun, 28 Jan 2018 23:17:24 +0000 Received: from momjian.us ([72.94.173.45]) by makus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.89) (envelope-from ) id 1efwCP-0005Vk-Ly for pgsql-docs@postgresql.org; Sun, 28 Jan 2018 23:17:23 +0000 Received: from bruce by momjian.us with local (Exim 4.84_2) (envelope-from ) id 1efwCN-0003xr-Tt; Sun, 28 Jan 2018 18:17:19 -0500 Date: Sun, 28 Jan 2018 18:17:19 -0500 From: Bruce Momjian To: Tom Lane Cc: Thomas Munro , ian@thepathcentral.com, pgsql-docs@postgresql.org, Andrew Gierth Subject: Re: Trigger behaviour not as stated Message-ID: <20180128231719.GC5022@momjian.us> References: <20171129193934.27108.30796@wrigleys.postgresql.org> <20180124181008.GK17109@momjian.us> <20180124220701.GP17109@momjian.us> <28238.1517167118@sss.pgh.pa.us> <20180128203402.GB4380@momjian.us> <15634.1517173027@sss.pgh.pa.us> <20180128225824.GA5022@momjian.us> <21622.1517181121@sss.pgh.pa.us> MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="zx4FCpZtqtKETZ7O" Content-Disposition: inline In-Reply-To: <21622.1517181121@sss.pgh.pa.us> User-Agent: Mutt/1.5.23 (2014-03-12) List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk --zx4FCpZtqtKETZ7O Content-Type: text/plain; charset=us-ascii Content-Disposition: inline On Sun, Jan 28, 2018 at 06:12:01PM -0500, Tom Lane wrote: > Bruce Momjian 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 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 + --zx4FCpZtqtKETZ7O Content-Type: text/x-diff; charset=us-ascii Content-Disposition: attachment; filename="trigger.diff" 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 column_name1 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 REFERENCING clause, then before and after images of rows are visible from all affected partitions or child tables. --- 501,510 ---- 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 REFERENCING clause, then before and after images of rows are visible from all affected partitions or child tables. --zx4FCpZtqtKETZ7O--