Re: Rules not executed on child tables - Mailing list pgsql-bugs

From Robert Haas
Subject Re: Rules not executed on child tables
Date
Msg-id AANLkTi=Lno4vk0TVqUnacm+dZy9StuxQpp59kXS-8Sx9@mail.gmail.com
Whole thread Raw
In response to Rules not executed on child tables  (<depstein@alliedtesting.com>)
List pgsql-bugs
On Wed, Aug 18, 2010 at 5:36 AM,  <depstein@alliedtesting.com> wrote:
> I noticed that when an action is executed on a parent table, rules for that
> action that are defined on its child tables are ignored.

I think this is actually design behavior.  It's really hard to use
rules for anything useful (other than views); you might want to look
at triggers instead.  Rules are basically a crude query-rewrite
system.  The rule rewriting process doesn't understand anything about
what your query is actually trying to do; it's just analyzing the
syntax (where, of course, the child tables aren't mentioned).

--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise Postgres Company

pgsql-bugs by date:

Previous
From: Ashesh Vashi
Date:
Subject: Re: BUG #5650: Postgres service showing as stopped when in fact it is running
Next
From: tkbysh2000@yahoo.co.jp
Date:
Subject: Re: BUG #5660: Can't start db service if specify effective_io_concurrency