From: | Christopher Browne <cbbrowne(at)gmail(dot)com> |
---|---|
To: | David Fetter <david(at)fetter(dot)org> |
Cc: | "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: Triggers on system catalog |
Date: | 2011-03-30 14:11:20 |
Message-ID: | AANLkTim1DSz7HFpufL2Ye0T5ucriR8CCupvM5NM8JsZ+@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Wed, Mar 30, 2011 at 9:59 AM, David Fetter <david(at)fetter(dot)org> wrote:
> On Tue, Mar 29, 2011 at 08:21:04PM -0400, Robert Haas wrote:
>> On Mar 29, 2011, at 2:17 PM, Christopher Browne <cbbrowne(at)gmail(dot)com> wrote:
>> > A proposal to adding triggers to system catalog tables won't be
>> > terribly popular.
>>
>> Well, I'd support it if I thought it had any chance of actually
>> working, but I don't.
>>
>> I do think we need some kind way of capturing DDL events, though. I
>> wonder if the object-access-hook stuff KaiGai and I did to support
>> SE-PostgreSQL could be extended to meet this need...
>
> Jan Wieck sketched out a proposal, which I'll post in more detail when
> I've transcribed it and checked that with him. Part of it is to fire
> triggers on the command completion code, and there are some code
> cleanups that that would depend on.
See <http://wiki.postgresql.org/wiki/DDL_Triggers>
That already captured an understanding of this, which might already be
nearly adequate.
--
http://linuxfinances.info/info/linuxdistributions.html
From | Date | Subject | |
---|---|---|---|
Next Message | Robert Haas | 2011-03-30 14:14:03 | Re: pg_dump --binary-upgrade vs. ALTER TYPE ... DROP ATTRIBUTE |
Previous Message | Merlin Moncure | 2011-03-30 14:05:51 | Re: Process local hint bit cache |