Re: CREATE OR REPLACE TRIGGER not supported?

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Christopher Kings-Lynne <chriskl(at)familyhealth(dot)com(dot)au>
Cc: Satoshi Nagayasu <nagayasus(at)nttdata(dot)co(dot)jp>, pgsql-hackers(at)postgresql(dot)org
Subject: Re: CREATE OR REPLACE TRIGGER not supported?
Date: 2004-09-13 03:00:19
Message-ID: 27420.1095044419@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Christopher Kings-Lynne <chriskl(at)familyhealth(dot)com(dot)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

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Daniel Schuchardt 2004-09-13 07:37:14 Re: beta1 & beta2 & Windows & heavy load
Previous Message Christopher Kings-Lynne 2004-09-13 01:31:52 Re: CREATE OR REPLACE TRIGGER not supported?