From: | Bruce Momjian <bruce(at)momjian(dot)us> |
---|---|
To: | ian(at)thepathcentral(dot)com |
Cc: | pgsql-docs(at)postgresql(dot)org |
Subject: | Re: Trigger behaviour not as stated |
Date: | 2018-01-24 18:10:08 |
Message-ID: | 20180124181008.GK17109@momjian.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-docs |
On Wed, Nov 29, 2017 at 07:39:34PM +0000, ian(at)thepathcentral(dot)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: "In contrast, row-level triggers are fired for all affected
> partitions or child tables."
>
> 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(at)momjian(dot)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 +
From | Date | Subject | |
---|---|---|---|
Next Message | Bruce Momjian | 2018-01-24 22:07:01 | Re: Trigger behaviour not as stated |
Previous Message | Daniel Gustafsson | 2018-01-24 08:56:07 | Re: PARALLEL in old syntax for CREATE AGGREGATE |