Re: Triggers on system catalog

From: Jim Nasby <jim(at)nasby(dot)net>
To: Jan Wieck <JanWieck(at)Yahoo(dot)com>
Cc: Robert Haas <robertmhaas(at)gmail(dot)com>, Stephen Frost <sfrost(at)snowman(dot)net>, Christopher Browne <cbbrowne(at)gmail(dot)com>, Shridhar Polas <shridharpolas(at)gmail(dot)com>, "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Triggers on system catalog
Date: 2011-04-06 14:54:59
Message-ID: D3BF2E50-B9DA-4EFB-8376-B692ED18D4FC@nasby.net
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Mar 30, 2011, at 3:45 PM, Jan Wieck wrote:
> What I would envision for DDL triggers is that they first don't fire on an object type, but rather on a command completion code, like "CREATE TABLE" or "DROP SCHEMA".
>
> To do anything useful with that of course would require that all DDL does go through tcop's ProcessUtility and actually synthesizes a proper Utility parsetree. That isn't the case today, so there would be some previous clean up work to be done.

For those that missed my announcement at PG East; we're willing to sponsor some/all of this work (depending on how much money we're talking).
--
Jim C. Nasby, Database Architect jim(at)nasby(dot)net
512.569.9461 (cell) http://jim.nasby.net

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Robert Haas 2011-04-06 14:56:48 Re: getting to beta
Previous Message Jim Nasby 2011-04-06 14:51:22 Re: Can I check if somebody is superuser in stored procedure?