Bruce Momjian wrote:
> Tom Lane wrote:
> 
>>Richard Huxton <dev(at)archonet(dot)com> writes:
>>
>>>Does that mean I'll want to disable triggers while I do this?
>>
>>Hrm.  Right now the code does not fire triggers at all, but that seems
>>wrong.  However, I doubt that very many triggers could cope with update
>>events in which the old and new rows have different rowtypes :-(.
>>Any thoughts what to do about that?
> 
> 
> If triggers exist, I think we should just throw a warning that triggers
> will not be fired.

Tom's point about triggers probably not working after the upgrade is a 
good one though. Is it reasonable to just refuse to act on a table until 
  all triggers are dropped? I'd rather be forced to go through and 
drop/restore triggers in a script than be surprised later on.

-- 
   Richard Huxton
   Archonet Ltd

In response to

• Re: ALTER TABLE TODO items at 2004-05-06 03:00:29 from Bruce Momjian

Responses

• Re: ALTER TABLE TODO items at 2004-05-06 15:47:13 from scott.marlowe

pgsql-hackers by date

Next:	From: Tony Reina	Date: 2004-05-06 08:22:45
	Subject: Re: Function to do runtime relative directory mapping
Previous:	From: Tatsuo Ishii	Date: 2004-05-06 07:40:34
	Subject: Re: PostgreSQL pre-fork speedup

pgsql-committers by date

Next:	From: Tom Lane	Date: 2004-05-06 14:01:33
	Subject: pgsql-server/src backend/nodes/outfuncs.c back ...
Previous:	From: Neil Conway	Date: 2004-05-06 06:11:01
	Subject: pgsql-server/src/backend/nodes nodes.c