Date: Wed, 24 Jan 2018 13:10:08 -0500
From: Bruce Momjian <bruce@momjian.us>
To: ian@thepathcentral.com
Cc: pgsql-docs@postgresql.org
Subject: Re: Trigger behaviour not as stated
Message-ID: <20180124181008.GK17109@momjian.us>
References: <20171129193934.27108.30796@wrigleys.postgresql.org>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20171129193934.27108.30796@wrigleys.postgresql.org>
User-Agent: Mutt/1.5.23 (2014-03-12)
Precedence: bulk

On Wed, Nov 29, 2017 at 07:39:34PM +0000, ian@thepathcentral.com wrote:
> The following documentation comment has been logged on the website:
> 
> Page: https://www.postgresql.org/docs/10/static/sql-createtrigger.html
> Description:
> 
> URL: https://www.postgresql.org/docs/current/static/sql-createtrigger.html
> 
> Statement: &quot;In contrast, row-level triggers are fired for all affected
> partitions or child tables.&quot;
> 
> Row-level triggers are not fired on child tables where the trigger ON BEFORE
> UPDATE | DELETE is on the parent table. Only works on BEFORE INSERT.

Uh, can you email us an example of the failure so we can research it? 
Thanks.

-- 
  Bruce Momjian  <bruce@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 +