Re: CREATE OR REPLACE TRIGGER not supported?

Christopher Kings-Lynne <chriskl@familyhealth.com.au> writes:
>> Is threre any reason not to support "CREATE OR REPLACE"
>> only for triggers?

> Because the oid of a trigger doesn't matter.  You can go being; drop 
> trigger; create trigger; commit; atomically.

And how often do you need to redefine a trigger (as opposed to its
underlying function), anyway?

Sure, given infinite manpower we would support this.  But it seems very
far down the to-do list to me.
        regards, tom lane