From: PG Doc comments form <noreply@postgresql.org>
To: pgsql-docs@lists.postgresql.org
Cc: pensnarik@gmail.com
Subject: Truncate statement-level trigger behaviour
Date: Tue, 27 Aug 2019 08:55:29 +0000
Message-ID: <156689612954.1127.4206178294202728291@wrigleys.postgresql.org> (raw)
The following documentation comment has been logged on the website:
Page: https://www.postgresql.org/docs/10/trigger-definition.html
Description:
Hello,
documentation
(https://www.postgresql.org/account/comments/new/10/trigger-definition.html/)
says:
"A statement that targets a parent table in an inheritance or partitioning
hierarchy does not cause the statement-level triggers of affected child
tables to be fired; only the parent table's statement-level triggers are
fired."
However, I noticed that statement-level TRUNCATE triggers are fired both for
parent table and its partitions. Is the documentation inconsistent with the
actual PostgreSQL behaviour or I missed something? I made some tests and
checked PostgreSQL source code as well (ExecuteTruncate() function) and it
seems that there is some inconsistency.
Thank you.
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-docs@postgresql.org
Cc: noreply@postgresql.org, pgsql-docs@lists.postgresql.org, pensnarik@gmail.com
Subject: Re: Truncate statement-level trigger behaviour
In-Reply-To: <156689612954.1127.4206178294202728291@wrigleys.postgresql.org>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox