From: | "Jim C(dot) Nasby" <jim(at)nasby(dot)net> |
---|---|
To: | Benjamin Krajmalnik <kraj(at)illumen(dot)com> |
Cc: | pgsql-admin(at)postgresql(dot)org |
Subject: | Re: Rules/Triggers executio order |
Date: | 2006-10-19 04:27:38 |
Message-ID: | 20061019042738.GD71084@nasby.net |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-admin |
On Wed, Oct 18, 2006 at 06:42:21PM -0600, Benjamin Krajmalnik wrote:
> I have a partitioned table to which I route data using a trigger.
> I am changing it to use a set of rules which executes "INSTEAD" on
> insert.
> The parent table currently has a trigger.
>
> The system is a live system. I would prefer to not have to suspend the
> data flow.
> If I create the rules, and given the fact that they execute "INSTEAD" of
> the insertion into the parent table, will the trigger still execute.
> I will be removing the trigger immediately after the creation of the
> rules, but just want to be safe and make sure I get no duplicate
> entries.
An INSTEAD OF rule replaces the query that you originally had with the
one re-written by the rule, so no, the triggers shouldn't fire. But you
should test to make sure.
--
Jim Nasby jim(at)nasby(dot)net
EnterpriseDB http://enterprisedb.com 512.569.9461 (cell)
From | Date | Subject | |
---|---|---|---|
Next Message | Cassiano, Marco | 2006-10-19 12:02:36 | Logfile permission |
Previous Message | Benjamin Krajmalnik | 2006-10-19 00:42:21 | Rules/Triggers executio order |