pg.ddx.io  pgsql-admin@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Benjamin Krajmalnik <kraj@illumen.com>
To: pgsql-admin@postgresql.org
Subject: Rules/Triggers executio order
Date: Wed, 18 Oct 2006 18:42:21 -0600
Message-ID: <F4E6A2751A2823418A21D4A160B68988315B@fletch.stackdump.local> (raw)

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.
 
Thanks in advance.

view thread (2+ messages)  latest in thread

Message-ID: <F4E6A2751A2823418A21D4A160B68988315B@fletch.stackdump.local>
Permalink:  ../F4E6A2751A2823418A21D4A160B68988315B@fletch.stackdump.local/
Also on:    postgresql.org/message-id/F4E6A2751A2823418A21D4A160B68988315B@fletch.stackdump.local

 · 

reply

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 from your mail client; the link fills in
  the headers below: reply via email
  Some clients, webmail especially, drop In-Reply-To and References from
  a link, and the reply then starts a new thread: use the mbox below.

  To: pgsql-admin@postgresql.org
  Cc: kraj@illumen.com
  Subject: Re: Rules/Triggers executio order
  In-Reply-To: <F4E6A2751A2823418A21D4A160B68988315B@fletch.stackdump.local>
  References: <F4E6A2751A2823418A21D4A160B68988315B@fletch.stackdump.local>

* 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